Buildroot Archive on 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 10:49:14 -0300	[thread overview]
Message-ID: <53F4A75A.1030505@zacarias.com.ar> (raw)
In-Reply-To: <20140820154213.00c239a8@free-electrons.com>

On 08/20/2014 10:42 AM, Thomas Petazzoni wrote:

> Right, but I believe it's two different (but related) matters:
> 
>  * On one hand, Mischa's approach is good to specify starting from
>    which gcc version this or that architecture or architecture variant
>    was supported. It allows to encode the "theory".
> 
>  * On the other hand, additional 'depends on' can be added
>    exceptionally to prevent certain gcc versions from being selected,
>    when they are supposed to work in theory, but in practice do not
>    work due to bugs (that are likely to be fixed in the next point
>    release).

True.
My basic aim here was to make things more legible when i was putting a
limit on power8 since it was too cluttered already with a single depends
being 300 characters wide - hardly legible and very prone to
mistakes/redundancy.
I think we can commit this and "upgrade it" so to speak when Mischa's
patchset is in to clean it up more.
Regards.

      reply	other threads:[~2014-08-20 13:49 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
2014-08-20 13:42     ` Thomas Petazzoni
2014-08-20 13:49       ` Gustavo Zacarias [this message]

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=53F4A75A.1030505@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox