[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Release update: kde3.3, upload targets, kernels, infrastructure

Hi Goto,

On Wed, Feb 02, 2005 at 01:54:54PM +0900, GOTO Masanori wrote:
> At Thu, 27 Jan 2005 07:30:57 -0800,
> Steve Langasek wrote:
> > On Thu, Jan 27, 2005 at 01:19:36PM +0100, Christoph Berg wrote:
> > > I upgraded a Woody box last week to Sarge's glibc/apt/dpkg/
> > > openoffice.org/perl last week. The result was that Woody's mysql does
> > > not work with Sarge's glibc. It complains about missing GLIBC_2.2
> > > symbols. I've then also upgraded mysql and things were fine again.

> > $ ldd -d -r /usr/bin/mysqladmin 
> >         libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x4002a000)
> >         libmysqlclient.so.10 => /usr/lib/libmysqlclient.so.10 (0x40073000)
> >         libz.so.1 => /usr/lib/libz.so.1 (0x400a9000)
> >         libcrypt.so.1 => /lib/tls/libcrypt.so.1 (0x400bb000)
> >         libnsl.so.1 => /lib/tls/libnsl.so.1 (0x400e8000)
> >         libm.so.6 => /lib/tls/libm.so.6 (0x400fc000)
> >         libc.so.6 => /lib/tls/libc.so.6 (0x4011e000)
> >         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
> > symbol errno, version GLIBC_2.0 not defined in file libc.so.6 with link time reference  (/usr/lib/libmysqlclient.so.10)

> I don't know this problem is "missing GLIBC_2.2 symbols" issue.  It
> does not clear Christoph's problematic architecture.

This is the only warning shown on my system when installing woody
mysqlclient on sarge glibc, and is the only major ABI regression of this
kind I'm aware of between woody and sarge glibc.  Unless Christoph can offer
more precise information about the symbols that were missing on his system,
I assume this is the problem he's referring to.

> > This is a bug in the woody libmysqlclient10 package, which should not have
> > been using errno in this way.

> > It also only occurs when the TLS-enabled glibc is used, which is only the
> > case if you are running a glibc kernel.

> IIRC that was already treated specially until sarge one year ago by
> Daniel.

I don't understand what you mean here.  How was it treated specially, and
why is it not treated specially now?

Steve Langasek
postmodern programmer

Attachment: signature.asc
Description: Digital signature

Reply to: