Hi
On Wed, Jan 17, 2007, Nelson A. de Oliveira wrote:
> Today pbuilder failed to get a build dependency on a i386 system with an
> amd64 chroot.
> The machine is amd64 (with amd64 kernel), but the installed system is
> i386.
So I think everything should now work in this setup, except that the
reported uname might affect builds.
If I understand correctly your setup, you had:
* x86-64 host running Debian i386 packages with x86-64 kernel
* i386 and/or amd64 chroots
I just added --architecture options to pbuilder and pdebuild to help
create chroots and do builds with other architectures:
pbuilder (0.196) unstable; urgency=low
[...]
* pbuilder: add support for setting the architecture on the command-line
and in pbuilderrc.
* pdebuild: add support for setting the architecture on the command-line
and in pbuilderrc; closes: #516625.
Both cases should work just fine:
- if you're building with an amd64 chroot with your x86-64 host kernel,
things should be fine
- if you're building with an i386 chroot with your x86-64 host kernel,
then things should more or less work, unless the package uses the
utsname/uname to conditionalize the build; I'm not sure whether this
is covered in policy or not. I know for sure that if you're building
on e.g. am i386 machine with SSE, the package should not assume it
can use it since it will be used on all i386 machines with some
lacking SSE, but I do not know whether packages might assume that the
kernel is 32-bits when building for i386. We could possibly make
pbuilder run linux32 in this case, but I'm not sure that's what we
want of policy say the packages should work in any case.
Would you mind checking whether anything is left to be done for this
bug?
Thanks,
--
Loïc Minier
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
