Yes, I did. However, it's not 100% tested and has it flaws, but it's possible
and if some buildsystem masters follow those steps, making it automated won't
be a big issue. Let's start. You need a fresh create-buildenv.sh first.

 - Create a new directory wherever you want. This directory will be an
alternative pacman cache for i686 packages. Let's say our dir is
/srv/store/drf/test32/pacmancache

 - Copy your pacman.conf to another location, and switch its architecture from
x86_64 to i686. All the repositories. Let's say our pacman.conf with i686
repositories is located at /srv/store/drf/test32/pacman32.conf

 - Now, in create-buildenv.sh, each call to pacman must have the following
additional options:

--cachedir /srv/store/drf/test32/pacmancache --config
/srv/store/drf/test32/pacman32.conf

So a sample pacman call would look like:

sudo pacman -r $BASEPATH/${REPO} --cachedir /srv/store/drf/test32/pacmancache
--config /srv/store/drf/test32/pacman32.conf -Sy $BASEPKGS

That's it. create your fresh new i686 chroot. Now there comes the bugs:

You have to switch the architecture everywhere else in the buildsystem
manually. Even if the system is i686, the buildsystem obviously doesn't know
that. So makepkg.conf and the stuff for upload (the 2 I run into, I bet
there's other stuff) need manual tweaks to work properly.

More than that, it's pretty much working. I just uploaded aqpm/shaman2/chase
in playground i686, a friend of mine just reported they work fine.

Now it's your turn to try and make this process suck less and be automated. Do
it and we can all switch to 64 bit and still build for everyone :) (and if
this gets done the possibility of having a build machine is more appealing)

--
-------------------

Dario Freddi
KDE Developer
GPG Key Signature: 511A9A3B

signature.asc < 1K Download