add patch to Autoconf 2.72 to ignore -target-feature flags when determining Fortran libraries#24669
Conversation
…ermining Fortran libraries
|
Test report by @Thyre |
|
Test of ELPA with this change: easybuilders/easybuild-easyblocks#3759 (comment) See #24516 (comment) for why we need this patch in the first place. |
|
@boegelbot please test @ jsc-zen3 |
|
@Thyre: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 3574732605 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
Test report by @jfgrimm |
|
Going in, thanks @Thyre! |
|
@boegelbot please test @ jsc-zen3 |
|
@jfgrimm: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 3575320375 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
(created using
eb --new-pr)See also: https://savannah.gnu.org/support/?111353
When building applications with LLVM/Clang, EasyBuild by default passes the flag
-march=nativetoconfigureto later on create an optimized build for his machine.Depending on the underlying system, this can lead to the following flag showing up in a verbose compiler output:
The Autoconf macro
_AC_FC_LIBRARY_LDFLAGSdetects the-lwpas a linker flag, and uses this one for further tests. Depending on the tests being done, this can either fail during configure itself, or later during the application build.A build failure was e.g. discovered with ELPA where this flag was being found in the linker step:
To fix this ignore all flags being passed via '-target-feature', as these are CPU feature flags, and do not represent actual libraries being linked.
For completeness, this is how a verbose output of LLVM 20.1.8 looks when building with
-march=native: