-
Notifications
You must be signed in to change notification settings - Fork 132
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
2024.08 is broken now: NQPCORE.setting fails to build #825
Comments
Can you check if a 2024.07 nqp + 143b5059c6fe9e5c8181bde40693995fb8c94dd0 moarvm also fails to build in a similar way? That is the first commit in moarvm after the 2024.07 release |
@timo Looks like:
Just in case, I checked if 2024.07 |
can you also share the output from moar configure and make steps? i'm trying to reproduce your trouble with a ppc and a ppc64 big endian container based on adelie linux (just the first thing I found) and while on the 64bit ppc i can successfully build a rakudo, i've still got some moarvm build trouble to resolve on the 32bit one, so i'm not getting close to to trying to build nqp yet |
I am away from the hardware for tonight, but I have used our existing portfiles. MacPorts is a bit tricky to run on Linux, but this should be reproducible without MacPorts. I only run build on MacOS though. No idea about the current MoarVM status on BSD and Linux. On MacOS I had no trouble to build MoarVM itself (the latest release), but that’s it. |
good news, I can reproduce the issue on both 32bit ppc big endian and 32bit x86. It looks like the in situ strings support isn't working with 32bit systems. Now I, or anyone really, should be able to debug and fix this without much hassle on a boring and common x86 or x86_64 machine! |
Please try if the latest commit to moarvm helps: MoarVM/MoarVM@f14712b6b9 |
Thank you, I will try today and update you. |
@timo I have built MoarVM 2024.08 with MoarVM/MoarVM@f14712b6b9 applied on top and tried to build
|
@timo Any update on the issue? Would be nice to have it working. |
I can't reproduce the failure that you're seeing. Could you run this from nqp's source directory?
I'm just assuming you have lldb but not gdb, since mac. Otherwise, this instead:
and give "y" for the "future shared library load" question, and another "y" or "n" if it asks about debugservers or anything. then when it hits the breakpoint in MVM_oops enter then
This is probably not going to give us terribly much info, but it will be a start ... |
ping @barracuda156 do you have time to look more into this soon? |
@timo Thanks for reminding. Will try tonight. BTW, only GDB is available, and rather old one, but it still works. |
hey @barracuda156 can you check with this moarvm commit i just pushed? MoarVM/MoarVM@e380dbabd6 I'm not sure it would actually ever trigger in a regular build, but when it goes wrong it can give the same error message as you got. |
@timo Thank you for an update. I rebuilt MoarVM 2024.08 with two patches applied – MoarVM/MoarVM@f14712b6b9 and MoarVM/MoarVM@e380dbabd6 – however still get the failure with
Did I miss some needed commit? |
I think you got all the interesting commits. Can you see if you can build moar with the |
@timo AFAIK, those gcc targets are not supported either outside of x86 or at least on PowerPC (on riscv64 they also do not build). |
2024.07 has build fine.
The text was updated successfully, but these errors were encountered: