summary refs log tree commit diff stats
path: root/results/scraper/box64/2456
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-16 14:55:48 +0200
committerChristian Krinitsin <mail@krinitsin.com>2025-07-16 14:55:48 +0200
commit63d2e9d409831aa8582787234cae4741847504b7 (patch)
tree595fae753d2eb293437226eaab2eed208463f132 /results/scraper/box64/2456
parent2843bb65aeaeb86eb89bf3d9690db61b9dc6306e (diff)
downloadqemu-analysis-63d2e9d409831aa8582787234cae4741847504b7.tar.gz
qemu-analysis-63d2e9d409831aa8582787234cae4741847504b7.zip
add box64 bug reports box64
Diffstat (limited to 'results/scraper/box64/2456')
-rw-r--r--results/scraper/box64/24566
1 files changed, 6 insertions, 0 deletions
diff --git a/results/scraper/box64/2456 b/results/scraper/box64/2456
new file mode 100644
index 000000000..277b2b890
--- /dev/null
+++ b/results/scraper/box64/2456
@@ -0,0 +1,6 @@
+Any tips on building box64 in a memory constrained environment?
+I'm trying to see if box64 will help me run an AppImage that for reasons can't be built on ARM. I'm on a Raspberry Pi 5 with 2GB ram and every time I try to build box64 and when following the [docs](https://github.com/ptitSeb/box64/blob/main/docs/COMPILE.md) every time I try to run `make -j4` it gets to 100% and then stalls out, running out of memory and terminating.
+
+I've tried everything I can think of to increase my total memory available (killing unnecessary process, allocation less to gpu, etc) but I just can't get the build to finish.
+
+Does anyone have any tips on ways to get box64 to build when your memory is constrained? 
\ No newline at end of file