From: "H. Peter Anvin" <hpa@zytor.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andreas Herrmann <aherrman@arcor.de>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Kconfig: ARCH=x86 causes wrong utsname.machine
Date: Fri, 16 Nov 2007 15:33:52 -0800 [thread overview]
Message-ID: <473E28E0.8050307@zytor.com> (raw)
In-Reply-To: <473E209A.7080806@zytor.com>
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
next prev parent reply other threads:[~2007-11-16 23:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 11:14 Kconfig: ARCH=x86 Andreas Herrmann
2007-11-16 12:37 ` Kconfig: ARCH=x86 causes wrong utsname.machine Andreas Herrmann
2007-11-16 15:20 ` H. Peter Anvin
2007-11-16 22:15 ` Sam Ravnborg
2007-11-16 22:58 ` H. Peter Anvin
2007-11-16 23:33 ` H. Peter Anvin [this message]
2007-11-17 7:57 ` Sam Ravnborg
2007-11-17 10:16 ` [PATCH] x86: fix UTS_MACHINE to be "i386" for 32-bit build and "x86_64" for 64-bit build Andreas Herrmann
2007-11-16 12:43 ` Kconfig: ARCH=x86 Andreas Herrmann
2007-11-16 12:58 ` Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=473E28E0.8050307@zytor.com \
--to=hpa@zytor.com \
--cc=aherrman@arcor.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox