public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Francesco Riosa <francesco@pnpitalia.it>
To: stuart@gentoo.org
Cc: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] mysql-bin ebuild
Date: Tue, 22 Feb 2005 20:28:49 +0100	[thread overview]
Message-ID: <421B87F1.2070608@pnpitalia.it> (raw)
In-Reply-To: <200502221846.03269.stuart@gentoo.org>

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
--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-02-22 19:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-22 12:55 [gentoo-dev] mysql-bin ebuild Francesco Riosa
2005-02-22 17:19 ` Robin H. Johnson
2005-02-24 11:57   ` Francesco Riosa
2005-02-24 19:36   ` Donnie Berkholz
2005-02-25  9:18     ` Francesco Riosa
2005-02-25 10:13       ` [gentoo-dev] -* v.s. package.mask Georgi Georgiev
2005-02-25 10:45         ` Francesco Riosa
2005-02-25 13:16         ` Ciaran McCreesh
2005-02-25 13:18         ` Chris Gianelloni
2005-02-25 11:40       ` [gentoo-dev] mysql-bin ebuild Martin Holzhauer
2005-02-25 12:44         ` Francesco Riosa
2005-02-27  1:26   ` Francesco Riosa
2005-02-22 18:46 ` Stuart Herbert
2005-02-22 19:28   ` Francesco Riosa [this message]
2005-02-22 20:11     ` Jeff Smelser
2005-02-23  2:20   ` Francesco Riosa
2005-02-22 19:03 ` Jeff Smelser
2005-02-22 19:35   ` Francesco Riosa
2005-02-22 20:17     ` Jeff Smelser
2005-02-22 20:26       ` Francesco Riosa
2005-02-24 14:40         ` Jeff Smelser
2005-02-24 15:12           ` Francesco Riosa
2005-02-24 15:12             ` Francesco Riosa
2005-02-24 15:28             ` Jeff Smelser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=421B87F1.2070608@pnpitalia.it \
    --to=francesco@pnpitalia.it \
    --cc=gentoo-dev@robin.gentoo.org \
    --cc=stuart@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox