compile error when emerging mysql-5.0.84-r1, with static compile option Reproducible: Always i installed a lower version of mysql(mysql-5.0.22) by compiling the source with the configure option: CFLAGS="-O3" CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions -fno-rtti" ./configure --prefix=/usr --sysconfdir=/etc --enable-assembler --with-pthread --enable-thread-safe-client --with-client-ldflags=-all-static --with-mysqld-ldflags=-all-static --with-charset=utf8 --with-extra-charsets=all --without-debug, no error appeared , but when initializing the database by "bin/mysql_install_db --user=mysql", mysqld process consumed 100% of CPU, and it lasted for a long time with nothing happen, i had to ctl+c to abort the process and killall mysqld, the result is failed then.
(In reply to comment #0) > compile error when emerging mysql-5.0.84-r1, with static compile option > > Reproducible: Always > > > > > i installed a lower version of mysql(mysql-5.0.22) by compiling the source with > the configure option: > CFLAGS="-O3" CXX=gcc CXXFLAGS="-O3 -felide-constructors -fno-exceptions > -fno-rtti" ./configure --prefix=/usr --sysconfdir=/etc --enable-assembler > --with-pthread --enable-thread-safe-client --with-client-ldflags=-all-static > --with-mysqld-ldflags=-all-static --with-charset=utf8 --with-extra-charsets=all > --without-debug, > no error appeared , but when initializing the database by "bin/mysql_install_db > --user=mysql", mysqld process consumed 100% of CPU, and it lasted for a long > time with nothing happen, i had to ctl+c to abort the process and killall > mysqld, the result is failed then. > well, i emerge again with no static option, it successful, but when doing "emerge --config =dev-db/mysql-5.0.84-r1", the symptom is the same as before i report.
Please add "emerge --info" output
a) We don't support versions of packages that aren't in the tree. b) We don't support building stuff from source without the package manger (and without an official gentoo ebuild) c) If you get compile errors with the static use flag for the in-tree versions, file a bug about it (if there isn't one). d) It's very likely that you screwed up your mysql installation. You installed two different versions with two different configurations. To fix it, first remove the version installed by the ebuild. Then run "make uninstall" in the source directory of the other mysql installation to get rid of it. Then install by ebuild again. As workaround try using another in-tree version.
