Tiny Core Base > Raspberry Pi
armhf TC15
Juanito:
Does a swap partition or swap file help?
The last time I tried, I’m pretty sure it was an illegal instruction that stopped things.
polikuo:
I tried compiling on RPI4-4G instead of RPI4-8G to encourage swapping.
The process was killed when the swap usage was somewhere around 3G
On idle
--- Code: ---tc@pi4-1:~$ free -m
total used free shared buff/cache available
Mem: 3792 54 3697 11 41 3685
Swap: 40173 0 40173
--- End code ---
Right before the process was killed
--- Code: ---top - 17:28:24 up 19 min, 3 users, load average: 1.83, 1.21, 0.60
Tasks: 169 total, 1 running, 168 sleeping, 0 stopped, 0 zombie
%Cpu0 : 11.0/9.7 21[|| ] %Cpu1 : 10.3/6.8 17[|| ]
%Cpu2 : 6.0/3.3 9[| ] %Cpu3 : 7.2/4.6 12[|| ]
GiB Mem : 96.3/3.7 [||||||||| ] GiB Swap: 3.4/39.2 [| ]
--- End code ---
Paul_123:
That’s the same wall I ran into a few years back. I could not find any useful help with 32bit systems.
Would the Debian/RaspiOS package build scripts provide any useful help?
Juanito:
My last attempt fails with this:
--- Code: ---In file included from /mnt/sda8/usr/src/firefox-128.2.0/firefox-build-dir/dist/stl_wrappers/new:62:
configure pre-export export compile misc libs tools
warning /mnt/sda8/usr/src/firefox-128.2.0/firefox-build-dir/dist/system_wrappers/new:3:15: fatal error: 'new' file not found
--- End code ---
Rich:
Hi polikuo
--- Quote from: polikuo on January 08, 2025, 10:59:29 PM ---I'm trying to compile firefox for armhf.
I'm having memory problem even though I'm using 64-bit kernel.
--- Code: ---tc@pi4-1:/mnt/mmcblk0p5/compile/firefox-128.6.0$ getBuild
armhf
tc@pi4-1:/mnt/mmcblk0p5/compile/firefox-128.6.0$ uname -m
aarch64
--- End code ---
I've tried limiting the job count to 1, but I'm still out of memory.
on idle:
--- Code: ---tc@pi4-1:/mnt/mmcblk0p5/compile/firefox-128.6.0$ free -m
total used free shared buff/cache available
Mem: 7809 1686 4016 79 2333 6123
Swap: 11046 2439 8606
--- End code ---
...
--- End quote ---
You're using a 64bit kernel, but a 32 bit toolchain. Right?
So that means the 64 bit kernel can allocate all available
RAM to various running apps.
But any 32 bit app needing more than 3.5 - 4 Gig of RAM
will still run out of memory because it can't address it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version