[01:30] *** kjp left
[01:34] *** kjp joined
[02:51] *** harrow left
[03:05] *** harrow joined
[11:55] *** [Coke] left
[13:37] *** [Coke] joined
[14:24] *** librasteve_ joined
[18:12] *** MasterDuke joined
[18:13] <MasterDuke> timo, patrickb, et al.: do you have any suggestions for https://github.com/MoarVM/MoarVM/pull/1967 ?

[18:13] <tellable6> 2026-05-10T23:36:30Z #raku-dev <[Coke]> masterduke snyk invite sent

[18:13] <MasterDuke> [Coke]: thanks

[18:14] <MasterDuke> that PR will let us remove dyncall, which will get our clang CI jobs green again

[18:25] <lizmat> testing on that PR is pretty red though?

[18:29] <MasterDuke> well, i have every build system i've ever used. it works locally (i.e., MoarVM+NQP+Rakudu all build), but there's a chicken-and-egg problem

[18:29] <MasterDuke> s/have/hate/

[18:32] <MasterDuke> i think the details are if you start from scratch, you don't have libffi.h. moar depends on libffi in the Makefile, but i believe that's only for the final stages? so it starts to compile moarvm, but can't find libffi.h

[18:32] <MasterDuke> and it's just a race condition if you use `-j`

[18:34] <lizmat> ok, fair enough...  but we're close to the release, so [Coke] should really be in on this

[18:34] <MasterDuke> configuring with `--has-libffi` might work, since that might assume there's a system libffi.h available

[18:35] <MasterDuke> no particular urgency, i wouldn't try for this next release

[18:35] <MasterDuke> just pinging people when i happen to be on

[18:36] <[Coke]> if the build doesn't work with -j it's broken

[18:43] <MasterDuke> i'll be on and off, but will check logs if there are any suggestions

[19:08] *** MasterDuke left
[20:00] *** rakkable left
[20:01] *** rakkable joined
[22:08] *** ShimmerFairy left
[22:08] *** ShimmerFairy joined