From: Sven Neumann <s.neumann@phase-zero.de>
To: buildroot@busybox.net
Subject: [Buildroot] gcc 4.3.3 anyone?
Date: Mon, 02 Feb 2009 18:02:26 +0100 [thread overview]
Message-ID: <1233594146.6464.6.camel@sven> (raw)
Hi,
I've ran into what appears to be a bug in gcc 4.3.2 and reported it
here: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39076
Now I consider to try to update buildroot to use gcc 4.3.3. But as there
are a number of patches for each gcc version this could become quite
some work. That's why I'm asking if anyone has already done that and
wants to share his/her experience/patches?
Sven
next reply other threads:[~2009-02-02 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 17:02 Sven Neumann [this message]
2009-02-02 20:06 ` [Buildroot] gcc 4.3.3 anyone? Peter Korsgaard
2009-02-05 9:59 ` Sven Neumann
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=1233594146.6464.6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.