Fails with clang: error: clang frontend command failed with exit code 139 (use -v to see invocation)

[makermelissa]

I have a Raspberry Pi Zero 2W with the RaSCSI Zero 1.0 FULLSPEC version. I started with a clean image of Raspberry Pi OS 64-bit, logged in and updated/upgraded. I followed the instructions to install PiSCSI, ran the easysetup.sh and while it was compiling, it stops at:

clang: error: clang frontend command failed with exit code 139 (use -v to see invocation) Debian clang version 14.0.6 Target: aarch64-unknown-linux-gnu Thread model: posix InstalledDir: /usr/bin clang: note: diagnostic msg:

---

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: clang: note: diagnostic msg: /tmp/piscsi_interface-51c09c.cpp clang: note: diagnostic msg: /tmp/piscsi_interface-51c09c.sh clang: note: diagnostic msg:

---

make: *** [Makefile:177: obj/piscsi_interface.pb.o] Error 139

[rdmark]

At a glance this looks like the same issue that was discussed at our Discord channel the other day. While it wasn't clear exactly what worked for that person, I think dropping down to a single thread for the clang compiler did the trick.

https://discord.com/channels/749261651978748014/754793914300629114/1329819405969915977

If you haven't joined our channel yet, head over to https://github.com/PiSCSI/piscsi/wiki#want-to-chat for the invite URL.

[makermelissa]

Thanks. I ended up using the premade image to go forward.

[sadguitarius]

I've never been able to get parallel builds of PiSCSI working. What did end up working great for me was distcc. Takes a bit to get it set up but once I did, it cut down on build time by a ton. In case you do ever need to do a custom build for any reason, or get PiSCSI running on another distribution

[rdmark]

This is the compiler using up all of the memory on the RPi and crashing with OOM. It is better to cross compile for either of the Zero models.