This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Saturday 13 August 2005 05:25 am, Lennert Buytenhek wrote: > On Sat, Aug 13, 2005 at 04:43:04AM -0400, Mike Frysinger wrote: > > also, the patch applies against 3.3.6 with a little fuzz, but clean > > enough to be usuable > > On a related note, have you been able to make gcc compile itself using > anything later than 3.3.3? i use 3.4.4 on arm/glibc, arm/uclibc, and armeb/uclibc without much hassle ... i just started developing on armeb so i havent done any glibc work yet (which i assume is what you're working with) i used to play with 3.3.[3-6] on arm/glibc but that was too much of a pain so i've switched to 3.4.4 now > Basically, using a crosstool toolchain with gcc version X (build=i686 > host=i686 target=armeb) to cross-compile a native gcc version Y > (build=i686 host=armeb target=armeb) produces a defective gcc version > Y that segfaults on this trivial program: yeah, ive only used 3.4.4 on armeb, plus i'm doing uClibc env ... and your test program builds & runs fine :/ -mike ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |