From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Thiago_A._Corr=EAa?= Date: Fri, 21 Mar 2008 12:33:02 -0300 Subject: [Buildroot] svn commit: trunk/buildroot/toolchain/gcc/4.2.1: avr32_patches_break_x86 In-Reply-To: <46a136670803210824y45035bd4u50dfa5446b9e8003@mail.gmail.com> References: <20080321112103.A34573C2F3@busybox.net> <87lk4cxq51.fsf@macbook.be.48ers.dk> <46a136670803210455l30fffb0dx90c449c7aa5c551e@mail.gmail.com> <46a136670803210824y45035bd4u50dfa5446b9e8003@mail.gmail.com> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net It was a source download, I suspect the behavior might still be in there, I haven't tried yet. I was focusing on figuring out in which revision things got broken... unfortunally it takes over an hour to try each revision. It was a download from the same repository as the Atmel's ARM stuff, so, I guess it's now at www.at91.com ftp On Fri, Mar 21, 2008 at 12:24 PM, John Voltz wrote: > I'm doing a full build for x86 right now with gcc 4.2.1 and kernel 2.6.24.3. > I'm using all of the patches except for the AVR32 900 series. I want to see > how many of the problems remain or disappear. All of the AVR32 patches came > from Atmel's buildroot, so I don't think their version will work any > differently. > > Where is the prepatched gcc available from? Is this a binary or source code? > > John > > > > > On Fri, Mar 21, 2008 at 11:14 AM, Thiago A. Corr?a > wrote: > > > Actually, it was unstable before.... I lost the a whole week's work > > trying to figure out why init crashes, and still haven't figured out. > > Even tried different gcc versions. > > > > > > VFS: Mounted root (jffs2 filesystem). > > Freeing init memory: 64K (90000000 - 90010000) > > init[1]: segfault at 00000000 pc 00000000 sp 7f9aee9c ecr 20 > > init has generated signal 11 but has no handler for it > > Kernel panic - not syncing: Attempted to kill init! > > > > I'm going back revisions to find one that works (atmel's buildroot > > fork works). Perhaps we could use the external toolchain for now, as > > it was before, where it downloads a pre-patched gcc for AVR32 instead > > of applying patches. (?) > > > > Kind Regards, > > Thiago A. Correa > > > > On Fri, Mar 21, 2008 at 8:55 AM, John Voltz wrote: > > > I'd rather leave it unusable until Atmel (or someone else) can fix it > > > properly. It has caused way too many people headaches and wasted LOTS of > > > people's time tracking down the causes of bugs and weirdness. > > > > > > John > > > > > > > > > > > > > > > On Fri, Mar 21, 2008 at 7:39 AM, Peter Korsgaard > wrote: > > > > >>>>> "ninevoltz" == ninevoltz 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 > > > > _______________________________________________ > > > > buildroot mailing list > > > > buildroot at uclibc.org > > > > http://busybox.net/mailman/listinfo/buildroot > > > > > > > > > > > > > _______________________________________________ > > > buildroot mailing list > > > buildroot at uclibc.org > > > http://busybox.net/mailman/listinfo/buildroot > > > > > > >