Re: 32bit builds on x86-64 host.

2007-10-31 Thread Sam Ravnborg
On Wed, Oct 31, 2007 at 08:57:39AM +, Christoph Hellwig wrote: > On Tue, Oct 30, 2007 at 06:00:01PM -0700, Jeremy Fitzhardinge wrote: > > Christoph Hellwig wrote: > > > Which seems rather unnatural to me. All other merge architectures have > > > ARCH= where archdir is the name under arch, e.g.

Re: 32bit builds on x86-64 host.

2007-10-31 Thread Christoph Hellwig
On Tue, Oct 30, 2007 at 06:00:01PM -0700, Jeremy Fitzhardinge wrote: > Christoph Hellwig wrote: > > Which seems rather unnatural to me. All other merge architectures have > > ARCH= where archdir is the name under arch, e.g. mips, powerpc, > > s390. They then have a CONFIG_FOO_64 and set the utsna

Re: 32bit builds on x86-64 host.

2007-10-30 Thread H. Peter Anvin
Jeremy Fitzhardinge wrote: Christoph Hellwig wrote: Which seems rather unnatural to me. All other merge architectures have ARCH= where archdir is the name under arch, e.g. mips, powerpc, s390. They then have a CONFIG_FOO_64 and set the utsname and -m32/-m64 respectively. It would be nice if x

Re: 32bit builds on x86-64 host.

2007-10-30 Thread Jeremy Fitzhardinge
Christoph Hellwig wrote: > Which seems rather unnatural to me. All other merge architectures have > ARCH= where archdir is the name under arch, e.g. mips, powerpc, > s390. They then have a CONFIG_FOO_64 and set the utsname and -m32/-m64 > respectively. It would be nice if x86 could behave like a

Re: 32bit builds on x86-64 host.

2007-10-30 Thread Christoph Hellwig
On Mon, Oct 29, 2007 at 05:07:08PM -0700, H. Peter Anvin wrote: > Dave Jones wrote: > >Before the arch merge, I frequently would test 32bit compiles > >by doing make ARCH=i386 {bzImage/modules/file.o} > > > >Since commit 47572387d58a9584c60ebbbdee56fc92c627f16f > >how does one do this? > > > > mak

Re: 32bit builds on x86-64 host.

2007-10-29 Thread Dave Jones
On Mon, Oct 29, 2007 at 05:07:08PM -0700, H. Peter Anvin wrote: > Dave Jones wrote: > > Before the arch merge, I frequently would test 32bit compiles > > by doing make ARCH=i386 {bzImage/modules/file.o} > > > > Since commit 47572387d58a9584c60ebbbdee56fc92c627f16f > > how does one do this?

Re: 32bit builds on x86-64 host.

2007-10-29 Thread H. Peter Anvin
Dave Jones wrote: Before the arch merge, I frequently would test 32bit compiles by doing make ARCH=i386 {bzImage/modules/file.o} Since commit 47572387d58a9584c60ebbbdee56fc92c627f16f how does one do this? make ARCH=i386 {bzImage/modules/file.o} Amazing, isn't it? -hpa - To unsubscri

Re: 32bit builds on x86-64 host.

2007-10-29 Thread Al Viro
On Mon, Oct 29, 2007 at 07:32:31PM -0400, Dave Jones wrote: > Before the arch merge, I frequently would test 32bit compiles > by doing make ARCH=i386 {bzImage/modules/file.o} > > Since commit 47572387d58a9584c60ebbbdee56fc92c627f16f > how does one do this? Same. Top-level makefile kludges around

32bit builds on x86-64 host.

2007-10-29 Thread Dave Jones
Before the arch merge, I frequently would test 32bit compiles by doing make ARCH=i386 {bzImage/modules/file.o} Since commit 47572387d58a9584c60ebbbdee56fc92c627f16f how does one do this? Dave -- http://www.codemonkey.org.uk - To unsubscribe from this list: send the line "unsubscribe lin