Bug#360491: marked as done ("uname -m" broken in ia32 chroot)
Your message dated Tue, 04 Apr 2006 04:52:28 +0200
with message-id <4431DF6C.9030508@aurel32.net>
and subject line Bug#360491: "uname -m" broken in ia32 chroot
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libc6
Version: 2.3.6-3
Severity: important
When running an i386-linux-gnu chroot on an x86_64-linux-gnu host:
$ uname -m
x86_64
This seriously breaks lots of native autoconf checks. A massive number of
packages will FTBFS or work improperly when built inside the chroot.
I think uname() should have hardcoded (#ifdef __x86_64__) machine name instead
of asking Linux which doesn't always know.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-amd64-k8
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
-- no debconf information
--- End Message ---
--- Begin Message ---
Aurelien Jarno wrote:
Robert Millan wrote:
Package: libc6
Version: 2.3.6-3
Severity: important
When running an i386-linux-gnu chroot on an x86_64-linux-gnu host:
$ uname -m
x86_64
This seriously breaks lots of native autoconf checks. A massive
number of
packages will FTBFS or work improperly when built inside the chroot.
Just install linux32, and use this wrapper to run your code.
I think uname() should have hardcoded (#ifdef __x86_64__) machine name
instead
of asking Linux which doesn't always know.
Using this solution would mean that you can't detect if a 32-bit or a
64-bit kernel is running, which is sometimes necessary. This is not
acceptable.
As explained, this is actually not a bug, closing it.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
--- End Message ---
Reply to: