[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: glibc-2.3 libc_p.a and libpthread_p.a symbol conflicts
From: |
Andreas Jaeger |
Subject: |
Re: glibc-2.3 libc_p.a and libpthread_p.a symbol conflicts |
Date: |
Mon, 18 Aug 2003 11:27:14 +0200 |
User-agent: |
Gnus/5.1003 (Gnus v5.10.3) XEmacs/21.4 (Portable Code, linux) |
"Arthur S Naseef" <address@hidden> writes:
> Attempting to build a static, profiled executable with libc and libpthread
> results in a symbol conflicts on __flockfile, _IO_flockfile, __funlockfile,
> and _IO_funlockfile. Below are the specifics of the glibc versions with
> sample commands that can be used to detect the problem.
>
> Which library should be defining these? Why do both contain them?
for threaded applications, the functions have a different
implementation and therefore need to overwrite the non-thread case.
This works fine in general and should not case any problems. So, why
is it a problem for you?
Andreas
> Versions
> GLIBC 2.3 (seen with 2.3.1 and 2.3.2)
> Linuxthreads
>
> nm -D /lib/libc-2.3.1.so | grep lockfile
> 000621a0 T _IO_flockfile
> 000621e0 T _IO_ftrylockfile
> 00062220 T _IO_funlockfile
> 000621a0 W flockfile
> 000621e0 W ftrylockfile
> 00062220 W funlockfile
>
> nm -D /lib/libpthread.so.0 | grep lockfile
> 00009f50 T _IO_flockfile
> 00009f90 T _IO_ftrylockfile
> 00009f70 T _IO_funlockfile
> 00009f50 W flockfile
> 00009f90 W ftrylockfile
> 00009f70 W funlockfile
>
>
>
>
>
>
> _______________________________________________
> Bug-glibc mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-glibc
>
Andreas
--
Andreas Jaeger, address@hidden, http://www.suse.de/~aj
SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
pgpmygwFpL3mM.pgp
Description: PGP signature