From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [bugfix 1/1] mesa-xlib: workaround gcc 4.6.0 ICE
Date: Fri, 27 May 2011 18:11:38 +0100 [thread overview]
Message-ID: <1306516298.27470.289.camel@rex> (raw)
In-Reply-To: <1306488650.2525.396.camel@phil-desktop>
On Fri, 2011-05-27 at 10:30 +0100, Phil Blundell wrote:
> On Fri, 2011-05-27 at 09:54 +0100, Richard Purdie wrote:
> > Good question. I guess you're just changing the gcc version but using
> > the rest of that file?
> >
> > This is a tricky problem as we do want to include that for anyone using
> > gcc 4.6 as otherwise things break but as you say, can't impact someone
> > using that file but changing its values.
> >
> > I guess the solution will be to turn it into anonymous python checking
> > if we're:
> >
> > * using gcc 4.6
> > * building for arm
> > * using armv7 optimisations
> > * building mesa-xlib
> >
>
> Can we not just patch gcc to fix the ice? That seems like it would be
> the best answer.
>
> If that's difficult for some reason, and downgrading gcc isn't an option
> either for whatever reason, then it seems like the right thing is going
> to be to get mesa-xlib's do_configure() to sort it out.
>
> I'm not sure that anonymous python is going to work since there is no
> particularly good and reliable method of determining ahead of time what
> version of gcc is going to end up being used for the build.
I was thinking of the GCCVERSION variable which is used in that same
file and is probably a valid thing to do in this specific case.
Anyhow, it looks like we have a fix for the ICE (Nitin confirmed it
builds) which is much perferred and I'm going to wait for that,
thanks :)
Richard
next prev parent reply other threads:[~2011-05-27 17:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 20:41 [bugfix 0/1] workaround for gcc 4.6.0 issue on beagleboard nitin.a.kamble
2011-05-26 20:41 ` [bugfix 1/1] mesa-xlib: workaround gcc 4.6.0 ICE nitin.a.kamble
2011-05-26 21:16 ` Darren Hart
2011-05-26 21:22 ` Kamble, Nitin A
2011-05-26 23:33 ` Richard Purdie
2011-05-27 0:37 ` Khem Raj
2011-05-27 1:03 ` Kamble, Nitin A
2011-05-27 7:14 ` Koen Kooi
2011-05-27 8:54 ` Richard Purdie
2011-05-27 9:30 ` Phil Blundell
2011-05-27 17:11 ` Richard Purdie [this message]
2011-05-27 15:06 ` Phil Blundell
2011-05-27 17:13 ` Kamble, Nitin A
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=1306516298.27470.289.camel@rex \
--to=richard.purdie@linuxfoundation.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