public inbox for linux-parisc@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Jeroen Roovers <jer@gentoo.org>
Cc: linux-parisc@vger.kernel.org, Mike Frysinger <vapier@gentoo.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, 09 May 2013 15:14:51 +0200	[thread overview]
Message-ID: <518BA14B.4060808@gmx.de> (raw)
In-Reply-To: <20130509142823.444ac244@marga.jer-c2.orkz.net>

On 05/09/2013 02:28 PM, Jeroen Roovers wrote:
> On Thu,  9 May 2013 01:08:35 -0400
> Mike Frysinger <vapier@gentoo.org> 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?

Helge

  reply	other threads:[~2013-05-09 13:14 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 [this message]
2013-05-09 19:24     ` Mike Frysinger
  -- 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=518BA14B.4060808@gmx.de \
    --to=deller@gmx.de \
    --cc=dave.anglin@bell.net \
    --cc=jejb@parisc-linux.org \
    --cc=jer@gentoo.org \
    --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