Hello, In case I want to have XtraDB as default storage engine and INNOBASE option is unset, mariadb103-server failes to build with output: ===> Installing for mariadb103-server-10.3.10 ===> Checking if mariadb103-server already installed ===> Registering installation for mariadb103-server-10.3.10 pkg-static: Unable to access file /usr/ports/databases/mariadb103-server/work/stage/usr/local/bin/innochecksum:No such file or directory pkg-static: Unable to access file /usr/ports/databases/mariadb103-server/work/stage/usr/local/bin/mariabackup:No such file or directory pkg-static: Unable to access file /usr/ports/databases/mariadb103-server/work/stage/usr/local/bin/mbstream:No such file or directory *** Error code 74 Stop. make[1]: stopped in /usr/ports/databases/mariadb103-server *** Error code 1 # cat /var/db/ports/databases_mariadb103-server/options # This file is auto-generated by 'make config'. # Options for mariadb103-server-10.3.10 _OPTIONS_READ=mariadb103-server-10.3.10 _FILE_COMPLETE_OPTIONS_LIST=CONNECT_EXTRA DOCS WSREP GSSAPI_BASE GSSAPI_HEIMDAL GSSAPI_MIT GSSAPI_NONE LZ4 LZO SNAPPY ZSTD INNOBASE MROONGA OQGRAPH ROCKSDB SPHINX SPIDER TOKUDB XTRADB ZMQ MSGPACK OPTIONS_FILE_UNSET+=CONNECT_EXTRA OPTIONS_FILE_UNSET+=DOCS OPTIONS_FILE_UNSET+=WSREP OPTIONS_FILE_UNSET+=GSSAPI_BASE OPTIONS_FILE_UNSET+=GSSAPI_HEIMDAL OPTIONS_FILE_UNSET+=GSSAPI_MIT OPTIONS_FILE_SET+=GSSAPI_NONE OPTIONS_FILE_UNSET+=LZ4 OPTIONS_FILE_UNSET+=LZO OPTIONS_FILE_UNSET+=SNAPPY OPTIONS_FILE_UNSET+=ZSTD OPTIONS_FILE_UNSET+=INNOBASE OPTIONS_FILE_UNSET+=MROONGA OPTIONS_FILE_UNSET+=OQGRAPH OPTIONS_FILE_UNSET+=ROCKSDB OPTIONS_FILE_UNSET+=SPHINX OPTIONS_FILE_UNSET+=SPIDER OPTIONS_FILE_UNSET+=TOKUDB OPTIONS_FILE_SET+=XTRADB OPTIONS_FILE_UNSET+=ZMQ OPTIONS_FILE_UNSET+=MSGPACK Thank you, Bernard
Thanks for reporting! I'll try and fix that in the FreeBSD port. Can you please report that upstream (https://jira.mariadb.org) and add a link to this PR?
Yes, I can. But I'm not sure how to correctly explain this issue there.
(In reply to iron.udjin from comment #2) Not an issue if you can't fully explain. When I have the link, I'll add more info to the JIRA issue.
https://jira.mariadb.org/browse/MDEV-17560
Created attachment 198701 [details] svn diff for databases/mariadb103-server Can you please check if attached patch solves your issue? It is also a loss of functionality (but you may not need these binaries)
With this patch port buils fine. P.S: mariabackup binary doesn't work: # mariabackup --help Segmentation fault (core dumped) ...but it's another "story".
For what it's worth... The InnoDB and XtraDB engines are supposed to be drop-in replacements. The earlier MariaDB releases (up to and including 10.1) used XtraDB . Starting with version 10.2 MariaDB switched to using InnoDB again as the default provider for InnoBase tables. Please read https://mariadb.com/kb/en/library/why-does-mariadb-102-use-innodb-instead-of-xtradb/ Unless you require something that's in XtraDB but not in InnoDB it is advisable to use InnoDB.
Closed with r501746