This is the mail archive of the crossgcc@sources.redhat.com 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] |
Trilok Soni <trilok_ulug@yahoo.co.in> wrote: > munmap(0x40013000, 10) = 0 > --- SIGILL (Illegal instruction) @ 0 (0) --- > +++ killed by SIGILL +++ > > But it still exits with illigal instruction...why? Illegal instruction means usually opcode for a wrong CPU type like for i686 or Athlon in a i386 CPU. With ARM there can be similar things... What your ARM922T CPU requires for the code generation, ie. what is the default CPU your toolchain now produces code for? Maybe you cannot use a '--with-cpu=arm922t' (only a '--with-cpu=arm9') in the GCC configure and get your CPU being the default. But you can use a '-mcpu=arm920t' when building your glibc... All this depends on what extra patches were used for your gcc-3.2.3. Anyway the goal should be to get a C library customized for your exact CPU type and use the same '-mcpu=arm920t' option later in all code production. Tailoring your 'specs' file is one choice to get it to be the default. When you have succeeded to build GCC and glibc, you should now have the know-how to update the components separately. So you can try to edit your 'specs' and put the '-mcpu=arm920t' there and then use your GCC to build glibc-2.2.5 with this default. Cheers, Kai ------ 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] |