Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] core: fix setting of HOSTARCH
Date: Mon, 9 Nov 2015 23:17:37 +0100	[thread overview]
Message-ID: <20151109221737.GD5162@free.fr> (raw)
In-Reply-To: <564117BE.4050300@mind.be>

Arnout, All,

On 2015-11-09 23:01 +0100, Arnout Vandecappelle spake thusly:
> On 09-11-15 20:00, Yann E. MORIN wrote:
> > Currently, we set HOSTARCH to the output of `uname -m`. This gives us
> > the architecture as seen by the running kernel. For example, we would
> > end up with 'x86_64' for a 64-bit kernel running on an x86_64 processor.
[--SNIP--]
> > So, instead of relying on the output of `uname -r`, look for the host
> > gcc and extract the target it was configured to generate code for.
[--SNIP--]
> > +export HOSTARCH := $(shell gcc -v 2>&1 | \
> > +	sed -e '/^Target: \([^-]*\).*/!d' \
> > +	    -e 's//\1/' \
> > +	    -e 's/i.86/x86/' \
> > +	    -e 's/sun4u/sparc64/' \
> > +	    -e 's/arm.*/arm/' \
> > +	    -e 's/sa110/arm/' \
> > +	    -e 's/ppc64/powerpc64/' \
> > +	    -e 's/ppc/powerpc/' \
> > +	    -e 's/macppc/powerpc/' \
> > +	    -e 's/sh.*/sh/' )
> 
>  Since what we get here already are gcc tuples, the de-mangling shouldn't be
> needed, right?

I am not sure either way. Note that I only constrained the check on how
to retrieve the value, and expressely did not address the way we played
with it, so as to follow the path of least surprise.

However, we still have to de-mangle i.86 into x86 because that what
we're using everywhere. Also, we need to demangle arm.* into arm,
because arm may have some trailing stuff (like armv6) which still means
it's an arm. Ditto sh I guess. macppc I would guess (y the name of it)
that we really don't care about. sa110: are we really expecting to run
on that machine anyway?

We can further reduce the de-mangling in a later patch, however, it that
makes sense...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-11-09 22:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09 19:00 [Buildroot] [PATCH] core: fix setting of HOSTARCH Yann E. MORIN
2015-11-09 22:01 ` Arnout Vandecappelle
2015-11-09 22:17   ` Yann E. MORIN [this message]
2015-11-10 21:48     ` Arnout Vandecappelle
2015-11-11 22:53 ` Thomas Petazzoni
2015-11-11 22:58   ` Yann E. MORIN
2015-11-12  7:52     ` Peter Korsgaard
2015-11-12 17:35       ` Yann E. MORIN
2015-11-12  8:11   ` Peter Korsgaard
2015-11-12  8:28     ` Thomas Petazzoni
2015-11-12  8:49       ` Peter Korsgaard
2016-01-19 23:11 ` Peter Korsgaard

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=20151109221737.GD5162@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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