Build fails on raspberry pi, "Error 2"

SoftFever / OrcaSlicer

G-code generator for 3D printers (Bambu, Prusa, Voron, VzBot, RatRig, Creality, etc.)

https://discord.gg/P4VE9UY9gJ

GNU Affero General Public License v3.0

7.5k stars 901 forks source link

Build fails on raspberry pi, "Error 2" #4099

Closed Ender436 closed 6 months ago

Ender436 commented 9 months ago

OrcaSlicer Version

1.9.0 (I think, I just cloned the repository)

OS version

Latest version of Raspbian

Additional system information

Raspberry pi 5 8GB ram version

Printer

N/A

How to reproduce

Follow the Linux build instructions on a raspberry pi:

Clone repository
Run "./BuildLinux.sh -u" wait for it to finish
Run "./BuildLinux.sh -dsir"
The build fails at this point

Actual results

Everything seems to build fine for a while, until the build outputs those lines after finishing building dep_OCCT.

make[1]: [CMakeFiles/Makefile2:738: CMakeFiles/deps.dir/rule] Error 2 make: [Makefile:423: deps] Error 2

Expected results

It should continue to build

Project file & Debug log uploads

Don't see any generated logs

Checklist of files to include

[x] Log file
[x] Project file

DrKlipper commented 9 months ago

I think this is a RAM problem. grafik Tried it on my Pi 4 with 8GB and the RAM maxed out.

Ender436 commented 9 months ago

@DrKlipper Is there a way I can compile for Arm64 then on another computer? Also, I have increased the amount of swap available on my pi, but I guess how much is used during a successful build? Maybe it isn't enough.

DrKlipper commented 9 months ago

Hi ! So my results are as following:

Compiling on a Pi needs at some points ~12-13GB Ram. So I ended up adding 8GB of SWAP to the system, which works fine for me.
Compiling on a Pi 4 takes about 4-5 hours! It takes forever :-)
Running Orca on a Pi 4 is fine until you slice something and want to make changes to the rendered view (like rotating, panning, ...) This is nearly impossible. I suppose it's due to missing OpenGL Support ? So using Orca on a Pi 4 is a no-go at this point. Don't know if there are any compile options to use some other 3D acceleration ?
Next try for me will be a Pi 5. The soc is ~2-3 times faster. So compiling should be quicker and hopefully it's useable after compiling.

Hope this helps :-)

Ender436 commented 9 months ago

Thanks for all the help! I thought I'd just try running the build again after seeing your comment, and for some reason it decided to work that time, it did crash a couple times during the build, but I just ran the command again and it seemed to pick up where it had left off. Now the only problem I'm facing is that the projects page and the setup wizard are both unusable. Some other windows too, but others like the app settings and stuff are fine. The glitched windows seems like they're rendering, but the pixels are being offset or something, because the colors are present, just garbled. Here's a screenshot of the printers configuration window.

Ender436 commented 9 months ago

Running "export WEBKIT_DISABLE_COMPOSITING_MODE=1” and then running the appimage seemed to have fixed it.

github-actions[bot] commented 6 months ago

Orca bot: this issue is stale because it has been open for 90 days with no activity.