On Thu, Mar 7, 2013 at 1:28 PM, Stephan Bergmann <sbergman(a)redhat.com>wrote:
Building LibreOffice for x86_64 starting to fail in an odd way
recently, <
http://koji.fedoraproject.**org/koji/getfile?taskID=**
5091173&name=build.log&offset=**-4000<http://koji.fedoraprojec...;,
I stripped that down to what I would assume is a newly introduced bug in
how ld resolves weak references?
Given a test.s of
.text
> .globl main
> .type main, @function
> main:
> .quad x
> .weakref x,__pthread_key_create
>
"gcc test.s" builds fine, while "gcc test.s -lcom_err", i.e.,
including a
reference to some .so that in turn needs libpthread, fails with
/usr/bin/ld: /tmp/cckAPSW1.o: undefined reference to symbol
> '__pthread_key_create@(a)GLIBC_**2.2.5'
> /usr/bin/ld: note: '__pthread_key_create@(a)GLIBC_**2.2.5' is defined in
> DSO /lib64/libpthread.so.0 so try adding it to the linker command line
> /lib64/libpthread.so.0: could not read symbols: Invalid operation
> collect2: error: ld returned 1 exit status
>
The same works fine in F-18. The failing ld is "GNU ld version
2.23.52.0.1-4.fc19 20130226."
I ran into this with kismet, adding an '-lpthread' at the right spot fixed
it. I think it just got stricter again.
-J
--
http://cecinestpasunefromage.wordpress.com/
------------------------------------------------
in your fear, seek only peace
in your fear, seek only love
-d. bowie