[ARM Builds, Native hardware and qemu]

My main and first ARM platform i compile for is an Genesi Efika Smartbook, it made me realize how much of an plague .deb systems are..

also been messing more around with the Jolla phone i got, i must say its a quite good compiler..

Ever thought about chaining a couple of android phones to a compiler cluster?

Anyhow the qemu problem seems to be that it uses one core by default. I took a look at the qemu-binfmt: http://pastebin.com/yrLuuAKL

and so far i could figure out the binary does not get any cpu number info, so lets put an -smp 8 there.. wasn't sure whereto but i think i figured it out.

 

So currently. i have to assume qemu uses only one core in snail speed. (htop, may be right) i'm too lazy to do any speed tests but lets put an -smp 8

maybe, here? if [ $cpu != "arm" -a -x "/usr/bin/qemu-static-arm-binfmt -smp 8" ] ; aaannd..

I get:  chroot: failed to run command ?/bin/bash?: Exec format error.  So.. where to feed it.

Oh and i been getting on a FX-8320 near target system performance,

but with those make CFLAGS:  "-O2 -pipe -march=armv7-a -mfpu=neon -funsafe-math-optimizations -mfloat-abi=hard"

[ARM Builds, Native hardware and qemu]

Hello!

 

Since over half an year, if not longer i been messing around with Funtoo on ARM. 

I did notice weird things such as the now removed from portage qemu-user is really buggy at times and

having about the same performance at times as the System i tried building it for. 

So currently i either can test/figure out how app-emulation/qemu works for static/chroot's

or just have my Netbook sit in a corner trying to compile everything. (800mhz i.MX515).

But neither seems to be a good option as documentation is scarce for qemu, such as the default setup using only one core and Portage end up being such a pain after 500 packages been emerged, dependency resolve seems to take up to 20 minutes at times.

Also anyone been building on a ODROID ? I'm considering getting one as build system.