Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1.10
-
None
-
linux
-
10.1.12
Description
Hi ,
When I executed mysql_install_db ,I got a message :
error while loading shared libraries: libjemalloc.so.1: cannot open shared object file: No such file or directory
-bash-4.2$ ./mysql_install_db --defaults-file=/mariadb/cnf_home/3308.cnf --user=mysql --basedir=/mariadb/db_home/mariadb-10.1.10 --datadir=/mariadb/data_home/3308
Installing MariaDB/MySQL system tables in '/mariadb/data_home/3308' ...
/mariadb/db_home/mariadb-10.1.10/bin/mysqld: error while loading shared libraries: libjemalloc.so.1: cannot open shared object file: No such file or directory
I look at this binary tar file ,I can't find this library .
Is the binary tar file forget to put the libjemalloc.so library file ?
Attachments
Activity
Let's see if we can link generic tarball binaries with jemalloc statically. Then they won't have a run-time dependency.
binary tarballs will now be linked with a static jemalloc library and won't have run-time jemalloc dependency anymore
Hello
I have this same problem. I used the 10.1.10 linux 64 bit distribution
Since I did not see a relevant Release id for the projected fix ... I'm unsure of the Universe where this kind of fundamental issue can be "closed" with NO kind of work-around or alternative to get mariadb (aka mysql) on a linux box.
From my reading of the trail here, there will be something done. At some time, there will be an installer/tar that will work.
The rest of us wanting to get some miles running/using and evaluating mariadb are up the sxxx-creek with no paddle.
Unlike OS-specific packages, binary tarballs are generic, and also they cannot pull dependencies automatically. If you decide to use binary tarballs instead of OS-specific packages, you need to take care of the dependencies yourself. libjemalloc.so.1 is one of them, you need to find it and install it on your system (you didn't mention what system that is, so I cannot suggest where to look).