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] |
Actually, it was being compiled with "-mcpu=arm922t". I'm tried it again by setting the arch field so that it compiles using "-march=armv4" which seems to work better (better means that now instead of "illegal instruction" I get "kernel too old"). In theory "armv4t" should work but right now I'm trying to get it to build with the glibc configure flag --enable-kernel=2.6.9 and see how that works (not very well, I'll need to keep trying older versions of glibc). Andy -----Original Message----- From: martinwguy@gmail.com [mailto:martinwguy@gmail.com] On Behalf Of Martin Guy Sent: Monday, January 19, 2009 6:20 PM To: Andy Johnson Cc: crossgcc@sourceware.org Subject: Re: ARM illegal instruction On 1/19/09, Andy Johnson <ajohnson@aecno.com> wrote: > I set the cpu type to match the processor listed from my > embedded device's /proc/cpuinfo (ARM922Tid), but both C > and Java programs die with an illegal instruction error. I've had this when the C compiler was built for armv4t as it should, but the libraries built for the (unfortunately) default CPU of armv5t, which means clz instructions. try a shot of --with-cpu= g'luck m -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |