Open lizmat opened 3 months ago
Thanks for proxying this issue, @lizmat
1.
In general, please remember, the BASH tool star
downloads the git tag
ged MoarVM
, NQP
and rakudo
releases from GitHub and compiles them, exactly the same way as rakudo
itself does.
Later, the tool adds some defined modules via ZEF. And this is actually the only Star
differentiator to rakudo core
.
So, if a star build run
fails on any specific client, something must be wrong with / for rakudo core
on that client already.
2.
For me, this topic seems to be a more of a MoarVM
issue. At least that's my quick & dirty guess due to line 735
, failed to load library 'dynext/libperl6_ops_moar.so' [so, it wasn't successfully build before, right?]
3.
If my wild guess makes any sense for you, someone would have to look into MoarVM
. It would be great in this person would also look into an open Debian MoarVM issue.
4.
Seems like the Debian team has gcc v14
on their mind... as hey refer to the porting guide Not sure if the Raku team has already __ported___ everything... or if this is a topic for raku at all!??!
pinging @patrickbkr
pinging @patrickbkr
@lizmat @patrickbkr
-- @patrickbkr ping statistics ---
1 packets transmitted, ??? received, 100% packet loss, time 2months, 6days
Hey, sorry, I overlooked the ping.
I don't have a NetBSD system available. Do you know which factors are necessary to trigger the issue? Does it only happen on star/plain, CI/manual, NetBSD/OpenBSD/FreeBSD?
From: https://irclogs.raku.org/raku-beginner/2024-08-01.html#12:07