Re: Kconfig: ARCH=x86 causes wrong utsname.machine

> >
> >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 don't think that is even 
> remotely feasible.

I will try to cook up a patch that sets CONFIG_UTS_MACHINE
and then we will use that value unless it is undefined in which
case we fall back to UTS_MACHINE (as today).

	Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- [PATCH] x86: fix UTS_MACHINE to be "i386" for 32-bit build and "x86_64" for 64-bit build
  - From: Andreas Herrmann <[email protected]>

References:
- Kconfig: ARCH=x86
  - From: Andreas Herrmann <[email protected]>
- Kconfig: ARCH=x86 causes wrong utsname.machine
  - From: Andreas Herrmann <[email protected]>
- Re: Kconfig: ARCH=x86 causes wrong utsname.machine
  - From: "H. Peter Anvin" <[email protected]>
- Re: Kconfig: ARCH=x86 causes wrong utsname.machine
  - From: Sam Ravnborg <[email protected]>
- Re: Kconfig: ARCH=x86 causes wrong utsname.machine
  - From: "H. Peter Anvin" <[email protected]>

Prev by Date: Re: Is it possible to give the user the option to cancel forkbombs?
Next by Date: alpha: fix sg_page breakage
Previous by thread: Re: Kconfig: ARCH=x86 causes wrong utsname.machine
Next by thread: [PATCH] x86: fix UTS_MACHINE to be "i386" for 32-bit build and "x86_64" for 64-bit build
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]