Red Hat Bugzilla – Bug 564930
FTBFS bygfoot-2.3.2-1.fc13.1: ImplicitDSOLinking
Last modified: 2010-02-14 04:55:35 EST
bygfoot-2.3.2-1.fc13.1.src.rpm Failed To Build From Source against the rawhide tree. See http://fedoraproject.org/wiki/FTBFS for more information.
This failure is due to a change in the linker default behavior, which uncovered a fault in your package. See http://fedoraproject.org/wiki/Features/ChangeInImplicitDSOLinking .
If you believe this is actually a bug in another package, do NOT change the component in this bug or close this bug. Instead, add the appropriate bug number from the other package to the "Depends on" line in this bug. If the other package does not yet have a bug created that you think matches, please create one. Doing so helps us properly track bugs and their dependencies, just as we track package dependencies. (If you close this bug, and the other package is not fixed before the next FTBFS run, a new bug will get created. Please follow the above advice to avoid such duplication.)
Created attachment 392538 [details]
root.log for i386
Created attachment 392539 [details]
build.log for i386
Created attachment 392540 [details]
mock.log for i386
Created attachment 392541 [details]
root.log for x86_64
Created attachment 392542 [details]
build.log for x86_64
Created attachment 392543 [details]
mock.log for x86_64
/usr/bin/ld: game.o: undefined reference to symbol 'rint@@GLIBC_2.2.5'
/usr/bin/ld: note: 'rint@@GLIBC_2.2.5' is defined in DSO /lib64/libm.so.6 so try adding it to the linker command line
/lib64/libm.so.6: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
The thing is, this failed to build for both arches with the same message, and I ran all failed builds again before filing any bugs, so it failed to build on both arches at least twice...
I'm not so certain it's a false positive.
linker team, please review. I don't think this is a false positive.
Don't take care about the comment #7, i inadvertelysubmitted the change before having finished deleting the previous message.
As i said in devel m-l, the fix has been committed and package rebuilt before closing this ticket.