|
From: Rich C. <rc...@wi...> - 2015-04-08 13:35:17
|
I followed the instructions on this page (or one like it) https://en.opensuse.org/HCL:Chroot At the time, I downloaded openSUSE-Factory-ARM-JeOS.armv7-rootfs.armv7l-1.12.1-Build172.2.tbz like this for the current version wget http://download.opensuse.org/ports/armv7hl/factory/images/openSUSE-Factory-ARM-JeOS.armv7-rootfs.armv7l-1.12.1-Build288.4.tbz mkdir rootfs tar xvjf *Build288.4.tbz -C rootfs I installed 'qemu-linux-user', another linux os probably has a different name for the package. The currently installed qemu is 2.1.0. I then used the script below to start a new dev shell. Once in the shell, the first time I had to install the compiler, tools, etc: zypper ref zypper up zypper in gcc make SDL-devel automake autoconf subversion For mips or ppc, without JeOS, there should be a way to mount a distribution dvd of linux and install another platform. I'd have to look into it. Rich ----- #! /bin/bash if [ ! -e "/proc/sys/fs/binfmt_misc/arm" ]; then /usr/sbin/qemu-binfmt-conf.sh fi echo "mounting procs" mount --bind /proc rootfs/proc mount --bind /sys rootfs/sys mount --bind /dev rootfs/dev mount --bind ../../../github/odroid rootfs/usr/local/src/odroid cp /etc/resolv.conf rootfs/etc/ echo "starting chroot " chroot rootfs echo "un-mounting procs" umount rootfs/usr/local/src/odroid umount rootfs/dev umount rootfs/sys umount rootfs/proc ----- On Wed, 08 Apr 2015 09:29:55 +0200 Julian Seward <js...@ac...> wrote: > On 08/04/15 04:49, Rich Coe wrote: > > I had a working arm qemu implementation installed. > > That's interesting. Can you send some details of which (arm) distro you > are running and on which qemu version? Did you have to do any special > hoop-jumping to get the distro installed? > > > > When I run 'make regtest', vg fails with out of memory. > > The first time I did this, I figured that the qemu emulation was causing > > the issue, so I didn't pursue it. Perhaps there's some simple solution > > for fixing the 'out-of-memory' error. The allocated bytes looks like > > an overflow. > > > + Valgrind's memory management: out of memory: > > + newSuperblock's request for 4194304 bytes failed. > > + 4142292992 bytes have already been allocated. > > + Valgrind cannot continue. Sorry. > > I agree, that definitely doesn't look good. It shouldn't have failed in > the first place unless you have very low memory available in the guest and > don't have swap enabled for it. > > J > -- Rich Coe rc...@wi... |