You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hitting into the following issue when using Apple M1. Please check the log below:
> Program [/{proj}/build/database/MariaDB4j/base/bin/mysql_install_db, --auth-root-authentication-method=normal, --datadir=/{proj}/build/database/MariaDB4j/data, --basedir=/{proj}/build/database/MariaDB4j/base, --no-defaults, --force, --skip-name-resolve] (in working directory /{proj}/build/database/MariaDB4j/base) failed, exitValue=1, last 100 lines of console:
Installing MariaDB/MySQL system tables in '/{proj}/build/database/MariaDB4j/data' ...
......
The latest information about mysql_install_db is available at
https://mariadb.com/kb/en/installing-system-tables-mysql_install_db
You can find the latest source at https://downloads.mariadb.org and
the maria-discuss email list at https://launchpad.net/~maria-discuss
Please check all of the above before submitting a bug report
at https://mariadb.org/jira
dyld[89308]: Library not loaded: /usr/local/opt/lz4/lib/liblz4.1.dylib
Referenced from: /{proj}/build/database/MariaDB4j/base/bin/mysqld
Reason: tried: '/usr/local/opt/lz4/lib/liblz4.1.dylib' (no such file), '/usr/local/lib/liblz4.1.dylib' (no such file), '/usr/lib/liblz4.1.dylib' (no such file)
Homebrew is installed under /opt path in M1 chips, but the current install still looks for the x86_64 file location. Maybe same as https://github.com/vorburger/MariaDB4j/issues/497 but just want confirmation if they are for the same reason.
The text was updated successfully, but these errors were encountered:
Hitting into the following issue when using Apple M1. Please check the log below:
Homebrew is installed under
/opt
path in M1 chips, but the current install still looks for the x86_64 file location. Maybe same as https://github.com/vorburger/MariaDB4j/issues/497 but just want confirmation if they are for the same reason.The text was updated successfully, but these errors were encountered: