From: Mike Frysinger <vapier@gentoo.org>
To: Helge Deller <deller@gmx.de>
Cc: Jeroen Roovers <jer@gentoo.org>,
linux-parisc@vger.kernel.org,
"James E.J. Bottomley" <jejb@parisc-linux.org>,
John David Anglin <dave.anglin@bell.net>
Subject: Re: [PATCH] parisc: make default cross compiler search more robust
Date: Thu, 9 May 2013 15:24:20 -0400 [thread overview]
Message-ID: <201305091524.22938.vapier@gentoo.org> (raw)
In-Reply-To: <518BA14B.4060808@gmx.de>
[-- Attachment #1: Type: Text/Plain, Size: 1906 bytes --]
On Thursday 09 May 2013 09:14:51 Helge Deller wrote:
> On 05/09/2013 02:28 PM, Jeroen Roovers wrote:
> > On Thu, 9 May 2013 01:08:35 -0400 Mike Frysinger 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. This code
> >> will run for both native and cross builds when CROSS_COMPILE isn't
> >> explicitly set.
> >
> > Several architectures appear to use a scriptlet called
> > cc-cross-prefix for this. See scripts/Kbuild.include.
>
> That's cool :-)
>
> Basically this
>
> +ifneq ($(SUBARCH),$(ARCH))
> + ifeq ($(CROSS_COMPILE),)
> + CROSS_COMPILE := $(call cc-cross-prefix,
> hppa$(WIDTH)-linux- hppa$(WIDTH)-linux-gnu-)
> + endif
> endif
>
> should then be enough.
>
> Do we really need to search for:
> hppa1.1-unknown-linux-gnu
> hppa1.1-linux-gnu
> hppa1.1-linux
> hppa2.0-unknown-linux-gnu
> hppa2.0-linux-gnu
> hppa2.0-linux
> on 32bit?
Gentoo actively uses hppa1.1 and hppa2.0 (i'm not sure we have any systems
that don't use those). we've seen some projects key off of those tuples (like
gmp) to change code selection.
similarly, the reason i included -unknown- is that is the tuple we use in
Gentoo for our native toolchain. for 64bit ones, we've been using ${ARCH}64-
linux as it was only good for building the kernel ... it didn't include a C
lib itself.
along that last line, hppa is the only target anymore where we have a
dedicated 64bit compiler for the kernel. all the other ports have biarch
support in gcc/binutils :/.
CC_ARCHES = hppa$(WIDTH) hppa1.1 hppa2.0
CC_SUFFIXES = linux linux-gnu unknown-linux-gnu
CROSS_COMPILE := $(call cc-cross-prefix, \
$(foreach a,$(CC_ARCHES),$(foreach s,$(CC_SUFFIXES),$(a)-$(s)-)))
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-05-09 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 5:08 [PATCH] parisc: make default cross compiler search more robust Mike Frysinger
2013-05-09 12:28 ` Jeroen Roovers
2013-05-09 13:14 ` Helge Deller
2013-05-09 19:24 ` Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-16 19:32 Helge Deller
2013-05-17 18:25 ` Greg KH
2013-05-17 20:06 ` Helge Deller
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=201305091524.22938.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=jejb@parisc-linux.org \
--cc=jer@gentoo.org \
--cc=linux-parisc@vger.kernel.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