Bug#821182: “so that one build is done using a 32 bit kernel (686-PAE) and the other build is using a 64 bit kernel”

[Thorsten Glaser]

Hi *,

this is obviously a bug in the buildd setup, because:

tglase at tglase:~ $ uname -m
x86_64
tglase at tglase:~ $ linux32 uname -m
i686

When running a 32-bit system with a 64-bit kernel, one MUST¹ do this:

root at dev:~ # dpkg-divert --list | fgrep init                                                               
local diversion of /sbin/init to /sbin/init.real
root at dev:~ # cat /sbin/init
#!/bin/mksh-static
exec /usr/bin/linux32 /sbin/init.real "$@"

When running a 32-bit build on a 64-bit system, one MUST invoke
the build tool with linux32 as well, for example:

$ sudo linux32 cowbuilder …

Or “personality=linux32” in /etc/schroot/schroot.conf, as the
already present, commented-out, example shows.

My own packaging of BSD make similarily looks at uname output
to decide for what platform to build, and requires this; bmake
is packaged in Debian too and may or may not require this and/or
may currently have bugs due to this.

bye,
//mirabilos

① leading to a funny situation where I had to add “linux64”
  to the libvirt init script so it recognised the system as amd64,
  but that’s all correct
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg