Cédric Vincent

Hello @fluxer, By default, PRoot changes the [guest] current working directory to $PWD (ie. same as the host one). This is useful when launching programs in the guest rootfs using...

Hello Nicolas, > configure: creating ./config.status > ../../src/configure: xrealloc: ../bash/subst.c:5188: cannot allocate > 2097152 bytes (5230592 bytes allocated) > configure: error: write failure creating ./config.status > [...] > $wine_rules_file is...

Hello Nicolas, For information, the latest release (v4.0.0) emulates a bigger heap. This should workaround this issue, however I keep it open since it is not an acceptable fix to...

Hello @orent, Thanks for the bug report. I confirm; the -0 option of PRoot changes permissions right before a file is accessed by a process, and restores them rigth after....

Thanks for the detailed information! I ran fpc-2.6.0 from Debian Wheezy ARMhf under PRoot with success. I compared your logs against mine but they don't differ that much. That means...

I used a STiH416 B2020 board (ARMv7) where the host system is STLinux 2.4 and /proc/cpu/alignment is set to "signal+warn" (nothing was reported).

I'd like to test your binary too. Where can I download it?

I wonder if commit 54904cb6 fixes this issue (as I can see your binary has the .note.gnu.build-id section)

> How are you building PRoot? I build static releases with PRoot, QEMU user-mode, and a Slackware-ARM-14.1 rootfs: https://github.com/cedric-vincent/proot-static-build/blob/master/GNUmakefile#L13 Maybe I wrongly described register constraints for the ARM loader, that...

> I'm cross-compiling it using arm-linux-gnueabihf-gcc 4.5 toolchain, > downloaded from emdebian.org. I tried this toolchain: - it doesn't build the loader as-is because of unsupported comment format in the...