Red Hat Bugzilla – Bug 564802
FTBFS unbound-1.4.1-1.fc13: ImplicitDSOLinking
Last modified: 2010-04-26 19:27:57 EDT
unbound-1.4.1-1.fc13.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 391810 [details]
root.log for i386
Created attachment 391811 [details]
build.log for i386
Created attachment 391812 [details]
mock.log for i386
Created attachment 391813 [details]
root.log for x86_64
Created attachment 391814 [details]
build.log for x86_64
Created attachment 391815 [details]
mock.log for x86_64
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.
More information and reason for this action is here:
unbound-1.4.3-1.el5 has been submitted as an update for Fedora EPEL 5.
unbound-1.4.3-1.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update unbound'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/unbound-1.4.3-1.el5
unbound-1.4.3-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.