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] external toolchain: [ARC] gcc cpu parameter
Date: Sun, 23 Feb 2014 12:09:28 +0100	[thread overview]
Message-ID: <20140223110928.GA3342@free.fr> (raw)
In-Reply-To: <884EA965490E3C4D8E66AEF41E98025006C2AD@ezex10.ezchip.com>

Noam, Thomas, All,

On 2014-02-23 10:57 +0000, Noam Camus spake thusly:
> Using external toolchain than BR2_GCC_TARGET_CPU is passed to GCC by
> -mcpu 
> Using buildroot toolchain than BR2_GCC_TARGET_CPU is passed to configure
> by --with-cpu
> 
> ARC GCC likes to get -mcpu=ARC700
> However through configure I am not sure but I think that config.gcc
> script is involved and it likes to get arc*.

From what I can see in gcc master:
  - ./configure expects: --with-cpu=arc700
  - gcc expects        : -mpcu=ARC700

Yes, that's it... :-/

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:[~2014-02-23 11:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-23  8:28 [Buildroot] [PATCH] external toolchain: [ARC] gcc cpu parameter Noam Camus
2014-02-23  9:48 ` Thomas Petazzoni
2014-02-23 10:57   ` Noam Camus
2014-02-23 11:09     ` Yann E. MORIN [this message]
2014-02-23 11:11     ` Thomas Petazzoni
2014-02-24  1:43       ` Anton Kolesov
2014-08-03 13:01 ` Thomas Petazzoni

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=20140223110928.GA3342@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