On 10/16/2014 09:56 PM, aTc wrote:
I'll create a debian stable x64 chroot and see if i can get the stuff going in there.
getting cowbuilder going with it was quite easy, so here's the quick way to set that up:
download http://next.openpandora.org/base-testing-armhf.tar.xz
apt-get install ccache eatmydata qemu-user-static git-buildpackage
create ~/.gbp.conf with: [default]
[git-buildpackage] export-dir = ~/export builder = ARCH=armhf DIST=testing git-pbuilder -I -i -j2
(replace -j2 with the number of cores you want to use compiling. ARCH and DIST should probably be set somewhere else, but since we're not changing them that much this is fine for now)
and create a ~/.pbuilderrc with: COMPONENTS="main contrib non-free" export LD_PRELOAD="${LD_PRELOAD:+$LD_PRELOAD:}/usr/lib/libeatmydata/libeatmydata.so" export CCACHE_DIR="/var/cache/pbuilder/ccache" export PATH="/usr/lib/ccache:${PATH}" BINDMOUNTS="${CCACHE_DIR}" EXTRAPACKAGES="ccache eatmydata"
cp ~/.pbuilderrc /root/ (because it runs sudo, it sometimes only reads the config file from the root user, this makes things slightly more bullet proof when updating, or when running cowpoke)
cd /var/cache/pbuilder/ tar Jxvf base-testing-armhf.tar.xz
and done :)
building a package :
gbp-clone git://git.openpandora.org/xserver-xorg-video-fbturbo.git cd xserver-xorg-video-fbturbo git-buildpackage
everything ends up in ~/export (defined in ~/.gbp.conf)
Building is already a slow process, and using qemu makes it even slower, even with cowbuilder,ccache and eatmydata.
building fbturbo: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz : real 5m55.992s user 5m41.207s sys 0m7.683s
omap5432: real 2m0.723s user 1m21.860s sys 0m14.210s