From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc: Drop ARCH_FLAGS_FOR_TARGET usage
Date: Sun, 27 Apr 2014 09:33:31 +0100 [thread overview]
Message-ID: <1398587611.16672.287.camel@ted> (raw)
In-Reply-To: <CAMKF1sqSYANfi1XjgrjUwkB0+bDcj45Vzd05ANv=XZ5=dOgQbA@mail.gmail.com>
On Sat, 2014-04-26 at 22:05 -0700, Khem Raj wrote:
> On Sat, Apr 26, 2014 at 5:22 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > As far as I can tell this variable is now completely unneeded. It would
> > only ever get used in target builds and these are now correctly done
> > in the target environment namespace, not any of our cross environments.
> > As such, CC and other variables contain the correct compilers and other
> > tune options and these are correctly picked up when building libgcc,
> > libstdc++ and others.
> >
> > I tried to figure out where else these would make any sense and couldn't
> > find anything. Builds appear fine without them so lets drop the complexity
> > including the patch adding in this flag to gcc.
>
> AFAR these were needed when doing SDK builds which was a shortcoming
> in gcc itself
> have you tried a SDK build with it ?
Yes, it seems to build just fine...
Cheers,
Richard
prev parent reply other threads:[~2014-04-27 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-27 0:22 [PATCH] gcc: Drop ARCH_FLAGS_FOR_TARGET usage Richard Purdie
2014-04-27 5:05 ` Khem Raj
2014-04-27 8:33 ` Richard Purdie [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=1398587611.16672.287.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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