"Jeremy Brand, B.S." <[EMAIL PROTECTED]> writes:
> Thus spake Goswin von Brederlow:
>
>> I would suggest looking for the error somewhere else. Did you change
>> gcc or something?
>
> Nope, not at all. The only thing slightly libc related is our change
> in nsswitch.conf to use files ldap.
>
> # COLUMNS=150 dpkg -l |grep 'libc6' | awk '{print $1" "$2" "$3}'
> ii libc6 2.3.2.ds1-22
> ii libc6-dev 2.3.2.ds1-22
>
> This is the same output on all of the 3 extra machines I just ran
> dpkg-architecture on .
>
> However, I just tested this on some completely different amd64/sarge
> boxes; some of which were just installed days ago, and the error is
> still the same. All three systems I tested do not assign values to
> the output of dpkg-architecture.
What does your sources.list look like?
A freshly installed sarge chroot does not have this bug nor the normal
sarge system I have running.
[EMAIL PROTECTED]:~% sudo cdebootstrap sarge /mnt/sarge
file:///mnt/mirror/debian-amd64 --include=build-essential
[EMAIL PROTECTED]:~% sudo chroot /mnt/sarge dpkg-architecture
DEB_BUILD_ARCH=amd64
DEB_BUILD_GNU_CPU=x86_64
DEB_BUILD_GNU_SYSTEM=linux
DEB_BUILD_GNU_TYPE=x86_64-linux
DEB_HOST_ARCH=amd64
DEB_HOST_GNU_CPU=x86_64
DEB_HOST_GNU_SYSTEM=linux
DEB_HOST_GNU_TYPE=x86_64-linux
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
