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

Bug#307985: libc6: 2.3.5-1 ppc built lacks GLIBC_2.3.3 version in libpthread



On Sat, May 07, 2005 at 02:06:15PM +1000, Benjamin Herrenschmidt wrote:
> On Fri, 2005-05-06 at 23:09 -0400, Daniel Jacobowitz wrote:
> > On Sat, May 07, 2005 at 12:42:02PM +1000, Benjamin Herrenschmidt wrote:
> > > Package: libc6
> > > Version: 2.3.5-1
> > > Severity: normal
> > > 
> > > 
> > > The 2.3.5-1 ppc build present in experimental has a problem with
> > > libpthread-0.10.so binary. For some reason I haven't been able to
> > > explain, it lacks the version GLIBC_2.3.3 symbol (it does have 2.3.2
> > > and 2.3.4 and libc6 itself has them all).
> > > 
> > > This prevents running some binaries built on other distros like fedora
> > 
> > And what GLIBC_2.3.3 symbols does Fedora have?
> 
> Hi Daniel !
> 
> I was trying to use their build of openoffice 2, and got that:
> 
> oobenh@gaston:~$ oowriter
> /usr/lib/openoffice.org1.9.100/program/javaldx: /lib/libpthread.so.0: version `GLIBC_2.3.3' not found (required by /usr/lib/openoffice.org1.9.100/program/libuno_sal.so.3)
> /usr/lib/openoffice.org1.9.100/program/soffice.bin: /lib/libpthread.so.0: version `GLIBC_2.3.3' not found (required by /usr/lib/openoffice.org1.9.100/program/libuno_sal.so.3)
> 
> and I get that:
> 
> benh@gaston:~$ readelf -a /usr/lib/openoffice.org1.9.100/program/libuno_sal.so.3 | grep 2.3.3
>    339: 00000000    44 FUNC    GLOBAL DEFAULT  UND __pthread_register_cancel@GLIBC_2.3.3 (18)
>    667: 00000000    72 FUNC    WEAK   DEFAULT  UND __pthread_unwind_next@GLIBC_2.3.3 (18)
>    682: 00000000    28 FUNC    GLOBAL DEFAULT  UND __pthread_unregister_canc@GLIBC_2.3.3 (18)
>   150:   2 (UDK_3_0_0)     2 (UDK_3_0_0)     2 (UDK_3_0_0)    12 (GLIBC_2.3.3)
>   298:   a (GLIBC_2.0)     2 (UDK_3_0_0)     2 (UDK_3_0_0)    12 (GLIBC_2.3.3)
>   2a8:   2 (UDK_3_0_0)     a (GLIBC_2.0)    12 (GLIBC_2.3.3)   2 (UDK_3_0_0)
>   0x00d0:   Name: GLIBC_2.3.3  Flags: none  Version: 18
> 
> The underscores makes me think that it's a problem with openoffice trying to
> use some glibc private symbols, but then, I'm not glibc expert so I can't be
> too sure...
> 
> If it's indeed a problem with openoffice, let me know & close this bug, I'll go
> bother the fedora folks to get it fixed in their build :)

These symbols are part of NPTL cancellation handling.  They won't work
unless you run with NPTL.

-- 
Daniel Jacobowitz
CodeSourcery, LLC



Reply to: