[Slackbuilds-users] nodejs22 fails to build - internal compiler error

[Andrzej Telszewski]

On 28/06/2026 21:45, 414N wrote:
> Il 28/06/26 20:47, Andrzej Telszewski ha scritto:
>> Hi,
>>
>> while trying to build nodejs22, I receive the following compile error:
>>
>> In file included from ../../deps/v8/src/handles/persistent-handles.h:11,
>>                   from ../../deps/v8/src/heap/local-heap.h:19,
>>                   from ../../deps/v8/src/handles/local-handles.h:12,
>>                   from ../../deps/v8/src/execution/local-isolate.h:12,
>>                   from 
>> ../../deps/v8/src/execution/local-isolate-inl.h:9,
>>                   from ../../deps/v8/src/common/ptr-compr-inl.h:10,
>>                   from 
>> ../../deps/v8/src/execution/isolate-utils-inl.h:8,
>>                   from ../../deps/v8/src/objects/dictionary-inl.h:9,
>>                   from ../../deps/v8/src/objects/contexts-inl.h:11,
>>                   from ../../deps/v8/src/execution/isolate-inl.h:9,
>>                   from ../../deps/v8/src/heap/factory-inl.h:13,
>>                   from 
>> gen/torque-generated/src/builtins/string-trim-tq- csa.cc:21:
>> ../../deps/v8/src/api/api.h:313:80: internal compiler error: 
>> Segmentation fault
>> (...)
>>
>>
>> slackrepo reports:
>> Build time 223 min, peak load 18.85, peak memory 14647M, peak tmp 1031M
>>
>> I have 32 GiB RAM + 16 GiB swap, so I don't expect it's a low memory 
>> issue.
>>
>> Happened twice for the 2 last times I tried to update.
>>
>> Does anyone has any clue what might be wrong?
>
> I see these happening on my system from time to time, especially while 
> compiling projects that are on the heavier side, like nodejs, llvm, 
> qt6, webkit etc.
>
> I usually solve this by retrying a number of times (eventually using 
> ccache to do the rebuilds quicker), until the compilation job finishes 
> successfully.
>
> This probably stems from low-quality or degraded ram on the system 
> that fumbles up when the system is particularly stressed, as during 
> such compilation jobs.
>
>

Yeah, I guess that might be something along these lines.
My build environment is rather clean - I use slackrepo with chroot.
One change I've done recently was to move from qemu-nbd to loop device.
(I had the chroot rootfs provided by qemu-nbd from QCOW file image, now 
it's provided by ext4 file image with loop device.)