-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
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
aarch64-linux
bootstrap failure on patchelf
: undefined reference to `__aarch64_ldadd4_acq_rel'
#246147
Comments
The mysterious part is that community builders do not seem to fail to build on As if the library path lookup orders are different between the two. Could it be that |
The failing attribute is |
No, it's not diff -u <(cat /tmp/bad | unnix) <(cat /tmp/good | unnix)
--- /dev/fd/63 2023-07-30 08:26:51.561118824 +0100
+++ /dev/fd/62 2023-07-30 08:26:51.561118824 +0100
@@ -273,6 +273,8 @@
attempt to open /<<NIX>>/xgcc-12.3.0/lib/gcc/aarch64-unknown-linux-gnu/12.3.0/libgcc.so failed
attempt to open /<<NIX>>/xgcc-12.3.0/lib/gcc/aarch64-unknown-linux-gnu/12.3.0/libgcc.a succeeded
/<<NIX>>/xgcc-12.3.0/lib/gcc/aarch64-unknown-linux-gnu/12.3.0/libgcc.a
+(/<<NIX>>/xgcc-12.3.0/lib/gcc/aarch64-unknown-linux-gnu/12.3.0/libgcc.a)ldadd_4_4.o
+(/<<NIX>>/xgcc-12.3.0/lib/gcc/aarch64-unknown-linux-gnu/12.3.0/libgcc.a)lse-init.o
/<<NIX>>/xgcc-12.3.0/lib/gcc/aarch64-unknown-linux-gnu/12.3.0/libgcc.a
attempt to open /<<NIX>>/bootstrap-stage0-glibc-bootstrapFiles/lib/libgcc.so failed
attempt to open /<<NIX>>/bootstrap-stage0-glibc-bootstrapFiles/lib/libgcc.a failed I'll compare |
One of the archives looks fine, another reports corruption:
|
MIght be related to 70945eb |
Proposed the change as #246164 |
Closed by #246164, I assume. |
Describe the bug
On
staging-next
:Same failure on hydra: https://hydra.nixos.org/build/229663092
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Bisect was a bit unstable, but with enough
--rebuild
s it seemingly reliably points to commit 3d66844gcc: revert "do not install sys-include headers for cross-compilers."
.My speculation: before that change
g++-12
probably usedlibgcc_s.so
fromg++-8
(bad) andc++/include
fromg++-8
(bad) and happened to work. Nowg++-12
still useslibgcc_s.so
fromg++-8
(bad) andc++/include
fromg++-12
(good).The text was updated successfully, but these errors were encountered: