From: Paul DuBois <dubois@primate.wisc.edu>
To: monty@tcx.se, Kostas Gewrgiou <gewrgiou@imbc.gr>
Cc: linuxppc-dev@lists.linuxppc.org, debian-powerpc@lists.debian.org,
mysql@lists.mysql.com
Subject: Re: MySQL at Linux/PPC
Date: Thu, 14 Oct 1999 18:21:04 -0500 [thread overview]
Message-ID: <19991014182104.00401@primate.wisc.edu> (raw)
In-Reply-To: <14342.11583.486814.996737@monty.pp.sci.fi>; from Michael Widenius on Thu, Oct 14, 1999 at 10:27:35PM +0300
On Thu, Oct 14, 1999 at 10:27:35PM +0300, Michael Widenius wrote:
> >>>>> "Kostas" == Kostas Gewrgiou <gewrgiou@imbc.gr> writes:
>
> Kostas> After looking at Bug#: 5732 in RedHat's bugzilla,
> Kostas> (http://developer.redhat.com/bugzilla/show_bug.cgi?id=5732)
> Kostas> i found out why enabling LFS makes a bad mysql binary, quoting from the
> Kostas> description of the patch bug:
>
> Kostas> The configure scripts of patch-2.5 detect the LFS support in
> Kostas> glibc-2.1, but due to the lack of a definition of
> Kostas> _GNU_SOURCE, no prototypes for fseeko are declared. That way
> Kostas> the compiler thinks fseeko is taking a 32bit argument for
> Kostas> the offset, when in reality it takes a 64bit offset.
>
> Kostas> After compiling MySQL with -D_GNU_SOURCE (with LFS enabled) the problems
> Kostas> went away, i am not sure if defining _LARGEFILE_SOURCE is supposed to give
> Kostas> the fseeko declarations but if it is then its a bug in the glibc headers.
>
> Kostas> Kostas Gewrgiou.
>
> Hi!
>
> MySQL 3.22.27 and MySQL 3.23.4 and above we now detect the glibc
> version and will not use LFS if glibc < 2.1
>
> We have successfully compiled MySQL on RedHat 6.0 without having to
> patch anything, so it looks like this is now fixed.
>
> If you still get the problem on your machine with the above MySQL
> version, please mail me and we will look at it once more!
>
> Regards,
> Monty
I haven't tried 3.22.7, but 3.23.4 builds and run just
fine with LinuxPPC R5/Q3 on my PowerBook and on a G4/400.
The LFS problem doesn't occur like it did with earlier versions.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~1999-10-14 23:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <v04205500b4268e121b94@[38.26.1.185]>
1999-10-13 6:19 ` MySQL at Linux/PPC Kostas Gewrgiou
1999-10-13 17:49 ` Joel Klecker
1999-10-14 19:27 ` Michael Widenius
1999-10-14 23:21 ` Paul DuBois [this message]
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=19991014182104.00401@primate.wisc.edu \
--to=dubois@primate.wisc.edu \
--cc=debian-powerpc@lists.debian.org \
--cc=gewrgiou@imbc.gr \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=monty@tcx.se \
--cc=mysql@lists.mysql.com \
/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;
as well as URLs for NNTP newsgroup(s).