-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Tracker]: Some packages cannot be built because -no-undefined-version
is enabled by default in lld-17
#18810
Labels
Comments
licy183
added
bug report
Something is not working properly
untriaged
tracker
and removed
bug report
Something is not working properly
untriaged
labels
Dec 24, 2023
@licy183 Similar issue in
|
|
Duplicating it here.
|
Updating scite to
|
cc @MaskRay |
haampie
added a commit
to spack/spack
that referenced
this issue
Jun 12, 2024
lld 17 and higher error by default when a symbol is versioned with a non-existing version. That change exposed various issues in different packages: gentoo/gentoo#29097 (comment) termux/termux-packages#18810 zlib-ng/zlib-ng#1421 The issue was fixed in zlib-ng 2.1.2, so adding the flag `-Wl,--undefined-version` unconditionally only hides possible regressions in the package going forward. Further, use of `%cce@17` may not imply use of `lld` as a linker. I would suggest not to deal with `-Wl,--(no-)undefined-version` flags in Spack, because we don't control the choice of linker anyways -- it's not in the dag & we don't add -fuse-ld / -ld-path / -B type of LDFLAGS. Instead, fix the relevant packages if they fail to build.
I think can close this |
The latest victim of this issue was libbsd 344f345 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem description
Some packages declare more symbols than they should declare in
version script
, and cause problem when these packages are built with lld-17.A workaround for this is passing
-Wl,--undefined-version
to LDFLAGS, but it doesn't seem to be a proper way.What steps will reproduce the bug?
Rebuild a package.
Package list
The text was updated successfully, but these errors were encountered: