Skip to content

Conversation

giordano
Copy link
Member

I don't know how this has happened, because I thought this was resolved by JuliaPackaging/Yggdrasil@123ac9b (#10132) (and the path is right for x86_64, aarch64, and powerpc64le), but the compiler support libraries ended up again in lib/ instead of lib64/ for riscv64, so we have to repeat #402. I thought we had a test about this (create a C++ library, and link to it with cc), apparently we don't, probably we should, but I don't have the time to add it right now.

@giordano
Copy link
Member Author

Ok, I believe this should be working now, tests were failing before because I was testing clang as well: we're passing -L/opt/${target}/${target}/${lib64} -Wl,-rpath-link,/opt/${target}/${target}/${lib64} only to gcc, we may want to do it for clang too, but leaving that change for the future for the time being.

@giordano giordano merged commit 0abbe35 into master Jan 31, 2025
7 checks passed
@giordano giordano deleted the mg/riscv64-lib64 branch January 31, 2025 13:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant