From: Mike Frysinger <vapier@gentoo.org>
To: Grant Grundler <grantgrundler@gmail.com>
Cc: John David Anglin <dave.anglin@bell.net>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
"kyle@mcmartin.ca" <kyle@mcmartin.ca>,
"deller@gmx.de" <deller@gmx.de>,
"linux-parisc@vger.kernel.org" <linux-parisc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: [PATCH v2] parisc: dont unconditionally override CROSS_COMPILE for 64 bit.
Date: Tue, 28 Feb 2012 13:37:10 -0500 [thread overview]
Message-ID: <201202281337.14094.vapier@gentoo.org> (raw)
In-Reply-To: <CANEJEGv2Zgtd8TGOzSNO8opMLQT8RsGRP=m2rBPUBBOJ9f+fKQ@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1477 bytes --]
On Tuesday 28 February 2012 13:22:50 Grant Grundler wrote:
> On Tue, Feb 28, 2012 at 7:33 AM, John David Anglin wrote:
> > On 2/28/2012 10:21 AM, Mike Frysinger wrote:
> >> we've been using hppa2.0 for years. gnuconfig certainly recognizes it:
> >> $ grep hppa /usr/share/gnuconfig/config.**sub
> >>
> >> | h8300 | h8500 | hppa | hppa1.[01] | hppa2.0 | hppa2.0[nw] |
> >>
> >> hppa64 \
> >>
> >> | hppa-* | hppa1.[01]-* | hppa2.0-* | hppa2.0[nw]-* | hppa64-* \
> >>
> >> and i've seen diff projects key off of the hppa2.0* to enable newer
> >> features by
> >> default.
> >
> > Some of the above are specific to HP-UX, but hppa1.1, hppa2.0, hppa and
> > hppa64 are
> > valid for Linux based on config.guess.
>
> Mike, et al,
> I'd suggest NOT using hppa2.0 as a surrogate for 64-bit build. I'd prefer
> hppa64 if 64-bit is meant.
>
> hppa2.0 can also mean PA2.0 compliant binary compiled using ILP32 model.
> right?
i don't think that's what the proposed change does. James' patch runs $(CC)
to find the active tuple, then replaces the first part with "hppa64" to get a
64bit toolchain automatically. but that magic only works when the tuple is
"hppa-xxx" and so will fail when the system is using "hppa2.0-xxx".
short story: the proposed change will additionally support turning "hppa2.0-
linux-gnu" into "hppa64-linux-gnu" rather than the existing "only turns hppa-
linux-gnu" into "hppa64-linux-gnu".
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-28 18:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-26 23:26 [PATCH] parisc: dont unconditionally override CROSS_COMPILE for 64 bit Paul Gortmaker
2012-02-27 0:23 ` Mike Frysinger
2012-02-27 0:30 ` Paul Gortmaker
2012-02-27 15:14 ` John David Anglin
2012-02-27 16:28 ` Paul Gortmaker
2012-02-27 16:45 ` John David Anglin
2012-02-27 20:59 ` [PATCH v2] " Paul Gortmaker
2012-02-27 21:41 ` James Bottomley
2012-02-27 22:03 ` James Bottomley
2012-02-28 1:04 ` Mike Frysinger
2012-02-28 3:17 ` James Bottomley
2012-02-28 6:06 ` Mike Frysinger
2012-02-28 14:10 ` James Bottomley
2012-02-28 15:21 ` Mike Frysinger
2012-02-28 15:33 ` John David Anglin
[not found] ` <CANEJEGv2Zgtd8TGOzSNO8opMLQT8RsGRP=m2rBPUBBOJ9f+fKQ@mail.gmail.com>
2012-02-28 18:37 ` Mike Frysinger [this message]
2012-02-28 19:54 ` 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=201202281337.14094.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=grantgrundler@gmail.com \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
/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;
as well as URLs for NNTP newsgroup(s).