From: Sven Neumann <s.neumann@phase-zero.de>
To: buildroot@busybox.net
Subject: [Buildroot] gcc 4.3.3 anyone?
Date: Thu, 05 Feb 2009 10:59:14 +0100 [thread overview]
Message-ID: <1233827954.6323.3.camel@sven> (raw)
In-Reply-To: <873aewhadh.fsf@macbook.be.48ers.dk>
Hi,
On Mon, 2009-02-02 at 21:06 +0100, Peter Korsgaard wrote:
> Sven> I've ran into what appears to be a bug in gcc 4.3.2 and reported it
> Sven> here: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39076
The gcc people have fixed this problem in the gcc-4.3 branch. I verified
that the patch fixes the compiler segfault when compiling flac. Attached
is a patch for buildroot that incorporates this fix for gcc 4.3.2.
I also noticed that two of the patches in toolchain/gcc/4.3.2 don't end
in .patch and thus are not applied. Is this intentional?
Sven
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gcc-bugfix.diff
Type: text/x-patch
Size: 908 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090205/bbc89c33/attachment.bin>
next prev parent reply other threads:[~2009-02-05 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 17:02 [Buildroot] gcc 4.3.3 anyone? Sven Neumann
2009-02-02 20:06 ` Peter Korsgaard
2009-02-05 9:59 ` Sven Neumann [this message]
2009-02-05 11:06 ` Peter Korsgaard
2009-02-05 13:29 ` Peter Korsgaard
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=1233827954.6323.3.camel@sven \
--to=s.neumann@phase-zero.de \
--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