Skip to content

Colons added after library names in LIBS (autotools build) #4074

@d-torrance

Description

@d-torrance

Here's a weird issue I'm getting with the current draft of the spack package on Ubuntu 24.04:

checking for Fortran libraries of /opt/spack/opt/spack/linux-zen2/compiler-wrapper-1.0-cpbsuow6nma4ib5tcxdpqkl3m2dkxher/libexec/spack/gcc/gfortran...  -L/usr/lib/gcc/x86_64-linux-gnu/13 -L/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu -L/usr/lib/gcc/x86_64-linux-gnu/13/../../../../lib -L/lib/x86_64-linux-gnu -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/13/../../.. -lglpk -lmps -lmpfi -lmpfr -lgmpxx -lgmp -lgc -lgdbm -lgfortran -lm -lquadmath -lglpk: -lmps: -lmpfi: -lmpfr: -lgmpxx: -lgmp: -lgc: -lgdbm:

In particular, it ends with -lglpk: -lmps: -lmpfi: -lmpfr: -lgmpxx: -lgmp: -lgc: -lgdbm:. Where did those colons come from? And of course, the build fails as soon as configure tries to link something because these libraries don't exist.

Full log

Metadata

Metadata

Assignees

No one assigned

    Labels

    build issueplatform specific issues involving compiling M2, generating examples, or running tests

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions