From: Jeroen Roovers <jer@gentoo.org>
To: Helge Deller <deller@gmx.de>
Cc: linux-parisc@vger.kernel.org,
James Bottomley <James.Bottomley@HansenPartnership.com>,
John David Anglin <dave.anglin@bell.net>,
Mike Frysinger <vapier@gentoo.org>
Subject: Re: [PATCH] parisc: make default cross compiler search more robust (v4)
Date: Sun, 12 May 2013 20:33:41 +0200 [thread overview]
Message-ID: <20130512203341.22d34f99@marga.jer-c2.orkz.net> (raw)
In-Reply-To: <20130511215555.GA12893@p100.box>
On Sat, 11 May 2013 23:55:55 +0200
Helge Deller <deller@gmx.de> wrote:
> People/distros vary how they prefix the toolchain name for 64bit
> builds. Rather than enforce one convention over another, add a for
> loop which does a search for all the general prefixes.
>
> For 64bit builds, we now search for (in order):
> hppa64-unknown-linux-gnu
> hppa64-linux-gnu
> hppa64-linux
>
> For 32bit builds, we look for:
> hppa-unknown-linux-gnu
> hppa-linux-gnu
> hppa-linux
> hppa2.0-unknown-linux-gnu
> hppa2.0-linux-gnu
> hppa2.0-linux
> hppa1.1-unknown-linux-gnu
> hppa1.1-linux-gnu
> hppa1.1-linux
>
> This patch was initiated by Mike Frysinger, with feedback from Jeroen
> Roovers, John David Anglin and Helge Deller.
>
> CC: Mike Frysinger <vapier@gentoo.org>
> CC: Jeroen Roovers <jer@gentoo.org>
> Signed-off-by: John David Anglin <dave.anglin@bell.net>
> Signed-off-by: Helge Deller <deller@gmx.de>
Signed-off-by: Jeroen Roovers <jer@gentoo.org>
jer
prev parent reply other threads:[~2013-05-12 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-11 19:04 [PATCH] parisc: make default cross compiler search more robust (v3) Helge Deller
2013-05-11 19:13 ` John David Anglin
2013-05-11 21:55 ` [PATCH] parisc: make default cross compiler search more robust (v4) Helge Deller
2013-05-12 18:22 ` Mike Frysinger
2013-05-12 18:33 ` Jeroen Roovers [this message]
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=20130512203341.22d34f99@marga.jer-c2.orkz.net \
--to=jer@gentoo.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.org \
--cc=vapier@gentoo.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