Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc: Add ability for tune files to pass in configure options to gcc
Date: Mon, 01 Aug 2011 15:30:44 +0100	[thread overview]
Message-ID: <1312209045.30326.515.camel@phil-desktop> (raw)
In-Reply-To: <1312208500-13381-1-git-send-email-galak@kernel.crashing.org>

On Mon, 2011-08-01 at 09:21 -0500, Kumar Gala wrote:
> Added a ${GCC_EXTRA_OECONF} to the the building up of gcc's
> ${EXTRA_OECONF}.  This is similar to what we have in the glibc recipe
> files.
> 
> This allows for a tune file to add something like:
> 
> GCC_EXTRA_OECONF += "--with-cpu=e5500"
> 
> If needed.
> 
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>

Why is that desirable?  From the looks of that patch it will affect
gcc-cross as well as target gcc and, if you're going to do this, I think
you need to find some way to disambiguate the resulting compilers.
Otherwise there is going to be no way to predict what options ${CC} was
built with.  

Even for the on-target gcc case, if you are going to start putting
MACHINE-specific variables into the configure commandline then you need
to make sure that the output packages have an appropriate Architecture.
I don't think that's going to be the case at the moment.

p.





  reply	other threads:[~2011-08-01 14:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-01 14:21 [PATCH] gcc: Add ability for tune files to pass in configure options to gcc Kumar Gala
2011-08-01 14:30 ` Phil Blundell [this message]
2011-08-01 14:37   ` Kumar Gala
2011-08-01 16:07     ` Phil Blundell
2011-08-01 16:44       ` Tom Rini
2011-08-01 16:57         ` Richard Purdie
2011-08-02 13:11           ` Kumar Gala
2011-08-02 13:42             ` Richard Purdie
2011-08-08 16:32               ` Kumar Gala
2011-08-08 23:22                 ` Richard Purdie
2011-08-08 16:35             ` Kumar Gala
2011-08-08 19:33               ` Richard Purdie
2011-08-02 13:02         ` Phil Blundell

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=1312209045.30326.515.camel@phil-desktop \
    --to=philb@gnu.org \
    --cc=openembedded-core@lists.openembedded.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