-
Notifications
You must be signed in to change notification settings - Fork 29
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
perl-cross 1.5.3 + perl 5.40.0: Build failure while crosscompiling x86_64-linux-gnu -> riscv64-linux-gnu #147
Comments
Can you post config.log and config.sh from the failing build?
Looks like it mis-detects something about threads on the target.
|
Same here from x86_64-linux-gnu to m68k-linux-gnu on Gentoo. 5.38.2 still builds fine, so I don't think it's a Gentoo issue. |
It seems this is a general issue. Do not apply
fix the linker errors for (all?) cross-compilation combinations. Tested with x86_64-linux-gnu to {aarch64,loongarch64,powerpc64le,riscv64}-linux-gnu so far. s390x then fails with different errors. But this may be an other issue. |
That xconfig.h patch must be either applied everywhere, or not applied anywhere (but that would defeat its whole purpose — do at your own risk).
Normally config.h is only included via perl.h, which is patched, but in 5.40, locale.c also includes config.h directly and must be patched as well. Without that, you end up with most of miniperl built using xconfig.h but with locale.c built using config.h instead. And it fails to link then.
Pushed a fix, try it if possible.
Now this issue should be 100% reproducible, but it's not, for me at least, so I might be missing something else.
|
Confirmed that 3627973 fixes it for me. |
Yes, 3627973 fixes all build errors x86_64-linux-gnu to {aarch64,loongarch64,powerpc64le,riscv64,s390x}-linux-gnu which I have seen. Thank you very much! |
Trying to crosscompile perl 5.40.0 from x86_64-linux-gnu to riscv64-linux-gnu with perl-cross 1.5.3 results in
while linking the host miniperl.
Native x86_64-linux-gnu builds of perl 5.40.0 compile and work fine on the same box.
The text was updated successfully, but these errors were encountered: