Bug#640672: moving files to arch specific include breaks compilations with -m32

2011-09-13 Thread Sven Joachim
On 2011-09-13 21:04 +0200, Daniel Bayer wrote: > Now I updated to linux-libc-dev 3.0.0-3 to test. After this /usr/include/asm > is an empty directory which belongs to gcc-multilib: Congratulations, you have just rediscovered bug #638418. Cheers, Sven -- To UNSUBSCRIBE, email to debian

Bug#640672: moving files to arch specific include breaks compilations with -m32

2011-09-13 Thread Daniel Bayer
Hi! On Mon, Sep 12, 2011 at 10:29:30PM -0700, Steve Langasek wrote: > On Tue, Sep 06, 2011 at 03:14:58PM +0100, Ben Hutchings wrote: > > On Tue, 2011-09-06 at 14:44 +0200, Daniel Bayer wrote: > > > Package: linux-libc-dev > > > Version: 3.0.0-3 > > > Severity: normal > > > File: /usr/include/x86_6

Bug#640672: moving files to arch specific include breaks compilations with -m32

2011-09-12 Thread Steve Langasek
On Tue, Sep 06, 2011 at 03:14:58PM +0100, Ben Hutchings wrote: > On Tue, 2011-09-06 at 14:44 +0200, Daniel Bayer wrote: > > Package: linux-libc-dev > > Version: 3.0.0-3 > > Severity: normal > > File: /usr/include/x86_64-linux-gnu/asm/errno.h > > since asm/errno.h was moved to the arch specific sub

Bug#640672: moving files to arch specific include breaks compilations with -m32

2011-09-12 Thread Michael Tokarev
The same is obviously true the other way around: on a 32bit x86 userspace it was possible to compile 64bit binaries using -m64. Now this is broken in exactly the same way as it is for -m32 on 64bits. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubsc