All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] package/gcc: cleanup arch/cpu combinations
Date: Wed, 20 Aug 2014 09:26:48 -0300	[thread overview]
Message-ID: <53F49408.3050701@zacarias.com.ar> (raw)
In-Reply-To: <20140820142417.31c93ef2@free-electrons.com>

On 08/20/2014 09:24 AM, Thomas Petazzoni wrote:
> What do you think of a solution like:
> 
>   [Buildroot] [PATCH] toolchain/gcc: Introduce BR2_ARCH_HAS_GCC_x_y_PLUS
> 
> which Mischa Jonker posted a while ago (but didn't push strong enough
> to get it merged) ?

Hi.
I thought about that but it really doesn't help in this scenario in a
complete way, since a given gcc may be broken (like 4.9.x was for ppc
e500) even though it includes support because of bitrot or bugs, like
some sparc targets, or blackfin for that matter.
Regards.

  reply	other threads:[~2014-08-20 12:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 21:16 [Buildroot] [PATCHv2] package/gcc: cleanup arch/cpu combinations Gustavo Zacarias
2014-08-20 12:24 ` Thomas Petazzoni
2014-08-20 12:26   ` Gustavo Zacarias [this message]
2014-08-20 13:42     ` Thomas Petazzoni
2014-08-20 13:49       ` Gustavo Zacarias

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=53F49408.3050701@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.