Binutils, particularly the static linker does not have --sysroot support enabled. I need --sysroot support to in the static linker to further support things like being able to freeze the glibc ABI/API for applications (using a sysroot) while still possible rebasing the actually deployed glibc. This would allow Fedora the ability to perhaps define a longer term ABI/API for application development while still rebasing glibc every release e.g. you would run the applications on the newer glibc but avoid the newer features until you wanted to make them visible to applications. All of this would be done with development sysroots that together would constitute something like a Fedora SDK sysroot. To do any of this we need to start by enabling sysroot support in Fedora Rawhide and Fedora in general. Enabling sysroot support in binutils should have minimal impact on static linking performance, but we need to double check this works on all of our supported arches. The last time I tested this the 32-bit arm builds had regressions.
I could only find one testsuite failure with an ARM native binutils - the linker test for PR 14918. I do not know if this is a regression, but the failure should be an expected one, since for the ARM target this particular test will fail. I have checked in a patch to enable sysroot support for all native targets, including ARM. The patch also includes an update to the linker testsuite to skip the PR14918 test. If any other regressions or failures do show up then please let me know. Fixed in: binutils-2.27-6.fc26
Thanks Nick! I'll start using the new binutils and let you know if anything else falls out.
(In reply to Carlos O'Donell from comment #2) > Thanks Nick! I'll start using the new binutils and let you know if anything > else falls out. *sigh* Don't bother. It doesn't work. :-(. See: https://bugzilla.redhat.com/show_bug.cgi?id=1377803 https://bugzilla.redhat.com/show_bug.cgi?id=1377949 Guess I have some more tracking down to do.
Found it. I failed to set the default sysroot path for native builds, so the configure script was using: /usr/local/x86_64-unknown-linux-gnu/sys-root. This should now be fixed in: binutils-2.27-7.fc26 Please give it a go.
I have a feeling this is causing GHC dynamic linking of executables to Haskell libraries to fail on aarch64 and armv7hl. See bug 1386126.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.