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

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 "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/

---

• 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: How to disable ECC with bootparam ?
• Next by Date: RE: [patch 07/30] cpu alloc: IA64 support
• Previous by thread: Re: Kconfig: ARCH=x86 causes wrong utsname.machine
• Next by thread: Re: Kconfig: ARCH=x86 causes wrong utsname.machine
• 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]