-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
fixup-libgfortran.sh
: Use patchelf
instead of parsing ldd
output
#34155
Conversation
This should be less brittle, and even better, work on `musl` Also ask `$FC` where `libgfortran` lives if we have no dirname Ask `libgfortran` where to get its libraries, don't rely on recursive dep printing
@rana @shabmk As the two users in JuliaCI/julia-buildbot#102 that have expressed interest in musl CI/CD, do builds of this branch locally pass tests for you? I'm thinking there might be something wrong with our BinaryBuilder libgit2 binaries, seeing as those tests seem to fail immediately with I/O errors. |
I don't think our libgit2 has ever worked for musl. See also #28805. |
Moved on without |
I tested in a Docker container (Alpine 3.9) and I encountered a total of 9 failures (all from the file testset) and 10 errors (2 in Sockets due to running in Docker). I did get that same I/O error from libgit2 but oddly enough I did not hit #28805. |
This issue was brought to my attention. I compiled this branch on my musl-native system. The I ran the tests.
|
Full long in case it helps |
Is it possible this broke something on Aarch64? After rebasing #34326 on master (which includes this PR), testing failed:
|
This should be less brittle, and even better, work on
musl
Also ask
$FC
wherelibgfortran
lives if we have no dirnameAsk
libgfortran
where to get its libraries, don't rely on recursive dep printing