From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/toolchain/gcc/4.2.1: avr32_patches_break_x86
Date: Fri, 21 Mar 2008 12:39:22 +0100 [thread overview]
Message-ID: <87lk4cxq51.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20080321112103.A34573C2F3@busybox.net> (ninevoltz@uclibc.org's message of "Fri\, 21 Mar 2008 04\:21\:03 -0700 \(PDT\)")
>>>>> "ninevoltz" == ninevoltz <ninevoltz@uclibc.org> writes:
ninevoltz> Author: ninevoltz
ninevoltz> Date: 2008-03-21 04:21:02 -0700 (Fri, 21 Mar 2008)
ninevoltz> New Revision: 21439
ninevoltz> Log:
ninevoltz> current avr32 gcc patches break x86 and possibly other
ninevoltz> systems. moving bad patches to separate directory until a
ninevoltz> proper fix is made. discovered by jacmet and Dr. Nigel
ninevoltz> Kukard
Thanks!
So I take it that gcc 4.2.1 is broken on AVR32 now? Perhaps you could
add a conditional in gcc-uclibc-4.x.mk like the ones for ARM to apply
these patches for AVR32?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-03-21 11:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 11:21 [Buildroot] svn commit: trunk/buildroot/toolchain/gcc/4.2.1: avr32_patches_break_x86 ninevoltz at uclibc.org
2008-03-21 11:39 ` Peter Korsgaard [this message]
2008-03-21 11:55 ` John Voltz
2008-03-21 15:14 ` Thiago A. Corrêa
2008-03-21 15:24 ` John Voltz
2008-03-21 15:33 ` Thiago A. Corrêa
2008-03-21 15:44 ` John Voltz
[not found] ` <47E3D9E4.6000901@apss.it>
2008-03-21 16:31 ` John Voltz
2008-03-22 2:11 ` Thiago A. Corrêa
2008-03-25 22:58 ` [Buildroot] svn commit: trunk/buildroot/toolchain/gcc/4.2.1:avr32_patches_break_x86 Ulf Samuelsson
2008-03-21 17:21 ` [Buildroot] svn commit: trunk/buildroot/toolchain/gcc/4.2.1: avr32_patches_break_x86 Nigel Kukard
2008-03-21 17:23 ` John Voltz
2008-03-21 17:29 ` John Voltz
2008-03-21 17:32 ` Nigel Kukard
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=87lk4cxq51.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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