Stuart Herbert ha scritto:

On Tuesday 22 February 2005 12:55, Francesco Riosa wrote:

After some testing on MySQL ebuild for version 4.1.x and 5.0.x appear to
me that is very difficult have a stable version of those databases with
current glibc, gcc and maybe os-headers stable defaults (at least on x86
and amd64).

Adding a dev-db/mysql-bin package seems the only short-term viable
solution to have those versions of mysql in portage tree.


What is broken w/ the current stable glibc & gcc?

Best regards,
Stu

The compiled sources from have problems with both ssl and ndbcluster, logs at [1], description of at [2], running the mysql bundled tests show various problems, from segfaults to hanging.
On the same systems, running the MySQL compiled sources goes well.
Saying that the problem is given from glibc, gcc and os-headers may be a limited point of view, because MySQL server and libraryes link against zlib, ncurses, readline, tcpwrappers, openssl too.
Anyway it's motived from bugs at [3] and seems to be not limited to 4.1 and 5.0 series that I've tested.
The problems seems limited to the server because running a binary version from MySQL and connecting from a client built from my ebuilds goes fine.


I hope that Jeff Smelser is right saying that it's only a problem of mine, if so the need of a mysql-bin ebuild is drastically reduced ;)

[1] http://www.francesco-riosa.com/gentoo/old/logs/
[2] http://www.francesco-riosa.com/gentoo/old/logs/00README.txt
[3] http://bugs.mysql.com/bug.php?id=7851
   http://bugs.mysql.com/bug.php?id=7970
   http://bugs.mysql.com/bug.php?id=7971
--
[email protected] mailing list



Reply via email to