> >
> >Any good suggestions here???
> >UTS_MACHINE is set in top-level Makefile and if we specify
> >make ARCH=x86
> >we do not know if i386 or x86_&4 is correct until the configuration
> >has been read.
> >
> >Should we report a "make ARCH=x86" as uname -m == x86??
> >
>
> That would break 5
H. Peter Anvin wrote:
Should we report a "make ARCH=x86" as uname -m == x86??
That would break 5 years of a stable ABI. I don't think that is even
remotely feasible.
Make that 5 years for x86-64, 16 years for i386...
-hpa
-
To unsubscribe from this list: send the line
Sam Ravnborg wrote:
On Fri, Nov 16, 2007 at 07:20:15AM -0800, H. Peter Anvin wrote:
Andreas Herrmann wrote:
The new ARCH=x86 kernel build causes weired machine strings on 32-bit.
For a cross-compiled kernel I have
$ uname -m
x66_64
For a kernel natively built on a 32 bit
On Fri, Nov 16, 2007 at 07:20:15AM -0800, H. Peter Anvin wrote:
> Andreas Herrmann wrote:
> >The new ARCH=x86 kernel build causes weired machine strings on 32-bit.
> >For a cross-compiled kernel I have
> >
> > $ uname -m
> > x66_64
> >
> >For a kernel natively built on a 32 bit machine I
Andreas Herrmann wrote:
The new ARCH=x86 kernel build causes weired machine strings on 32-bit.
For a cross-compiled kernel I have
$ uname -m
x66_64
For a kernel natively built on a 32 bit machine I have
$ uname -m
x66
Looking at the sources, I think that
Hi Andreas.
On Fri, Nov 16, 2007 at 12:14:46PM +0100, Andreas Herrmann wrote:
> Hi,
>
> I have just some minor remarks wrt the commit message for
> daa93fab824f2b8c35bd11670c7fab2f32b2de5f - 'x86: enable "make
> ARCH=x86"'. (Based on my observations when testing the stuff on 64bit
> and 32bit
On Fri, Nov 16, 2007 at 12:14:46PM +0100, Andreas Herrmann wrote:
> BTW, is the x86 kernel build documented somewhere?
> At a first glance I didn't find anything suitable under Documentation/.
> Maybe some explanation (like the above) should be added there.
When the ARCH=x86 build is documented,
The new ARCH=x86 kernel build causes weired machine strings on 32-bit.
For a cross-compiled kernel I have
$ uname -m
x66_64
For a kernel natively built on a 32 bit machine I have
$ uname -m
x66
Looking at the sources, I think that utsname->machine was
Hi,
I have just some minor remarks wrt the commit message for
daa93fab824f2b8c35bd11670c7fab2f32b2de5f - 'x86: enable "make
ARCH=x86"'. (Based on my observations when testing the stuff on 64bit
and 32bit hosts with Linus' tree v2.6.24-rc2-640-g8c08634.)
For randconfig we have now the following
Hi,
I have just some minor remarks wrt the commit message for
daa93fab824f2b8c35bd11670c7fab2f32b2de5f - 'x86: enable make
ARCH=x86'. (Based on my observations when testing the stuff on 64bit
and 32bit hosts with Linus' tree v2.6.24-rc2-640-g8c08634.)
For randconfig we have now the following
The new ARCH=x86 kernel build causes weired machine strings on 32-bit.
For a cross-compiled kernel I have
$ uname -m
x66_64
For a kernel natively built on a 32 bit machine I have
$ uname -m
x66
Looking at the sources, I think that utsname-machine was
Andreas Herrmann wrote:
The new ARCH=x86 kernel build causes weired machine strings on 32-bit.
For a cross-compiled kernel I have
$ uname -m
x66_64
For a kernel natively built on a 32 bit machine I have
$ uname -m
x66
Looking at the sources, I think that
Hi Andreas.
On Fri, Nov 16, 2007 at 12:14:46PM +0100, Andreas Herrmann wrote:
Hi,
I have just some minor remarks wrt the commit message for
daa93fab824f2b8c35bd11670c7fab2f32b2de5f - 'x86: enable make
ARCH=x86'. (Based on my observations when testing the stuff on 64bit
and 32bit hosts with
On Fri, Nov 16, 2007 at 12:14:46PM +0100, Andreas Herrmann wrote:
BTW, is the x86 kernel build documented somewhere?
At a first glance I didn't find anything suitable under Documentation/.
Maybe some explanation (like the above) should be added there.
When the ARCH=x86 build is documented,
On Fri, Nov 16, 2007 at 07:20:15AM -0800, H. Peter Anvin wrote:
Andreas Herrmann wrote:
The new ARCH=x86 kernel build causes weired machine strings on 32-bit.
For a cross-compiled kernel I have
$ uname -m
x66_64
For a kernel natively built on a 32 bit machine I have
$
Sam Ravnborg wrote:
On Fri, Nov 16, 2007 at 07:20:15AM -0800, H. Peter Anvin wrote:
Andreas Herrmann wrote:
The new ARCH=x86 kernel build causes weired machine strings on 32-bit.
For a cross-compiled kernel I have
$ uname -m
x66_64
For a kernel natively built on a 32 bit
H. Peter Anvin wrote:
Should we report a make ARCH=x86 as uname -m == x86??
That would break 5 years of a stable ABI. I don't think that is even
remotely feasible.
Make that 5 years for x86-64, 16 years for i386...
-hpa
-
To unsubscribe from this list: send the line
Any good suggestions here???
UTS_MACHINE is set in top-level Makefile and if we specify
make ARCH=x86
we do not know if i386 or x86_4 is correct until the configuration
has been read.
Should we report a make ARCH=x86 as uname -m == x86??
That would break 5 years of a stable ABI. I
18 matches
Mail list logo
