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]

RE: What all should I take care while compiling and running?


> When I do:
> # file a.out
> on old (running) binary, it shows :
> a.out: ELF 32-bit LSB executable, ARM, version 1 (SYSV), for GNU/Linux
> 2.4.17, dynamically linked (uses shared libs), not stripped
> Which has " GNU/Linux 2.4.17 "  clearly diffrent from the new one
> ("GNU/Linux 2.4.3") , as Chuck said.
> 
> 
> I made changes to "crosstool.sh" in  crosstool-0.38:
> .....
> --enable-kernel=2.4.17
> ......
> 
> which was
> --enable-kernel=2.4.3
> earlier. Then I build new toolchain arm-9tdmi-linux-gnu.
> 
> Using new arm-9tdmi-linux-gnu I built, I do :
> 
> # arm-9tdmi-linux-gnu-gcc -static hello.c
> # ./a.out
> Illegal instruction
> # file a.out
> a.out: ELF 32-bit LSB executable, ARM, version 1 (ARM), for GNU/Linux
> 2.4.17, statically linked, not stripped
> 
> # arm-9tdmi-linux-gnu-gcc -shared hello.c
> # ./a.out
> Segmentation fault
> # file ./a.out gives
> a.out: ELF 32-bit LSB shared object, ARM, version 1 (ARM), not stripped
> 
> # arm-9tdmi-linux-gnu-gcc testcpro.c
> # ./a.out
> -sh: ./a.out: not found
> # file a.out
> a.out: ELF 32-bit LSB executable, ARM, version 1 (ARM), for GNU/Linux
> 2.4.17, dynamically linked (uses shared libs), not stripped
> 
> Here I can find another notable difference:
> " ARM, version 1 (SYSV), "
> and
> " ARM, version 1 (ARM), "
> 
> I hv tried with " --enable-kernel=2.6.10 " in " crosstool.sh " also.
> 
> Plz tell me the possibilities

I have not used tools built for arm-9tdmi.  Question for the list -- are
there instructions generated specific to the "9tdmi" that are specific to
later ARM CPU's?  The static binary that Pramod emailed out last night works
fine on my OSK target running Linux 2.6.10.  The very same binary gives him
an illegal instruction exception.  

Pramod -- what exact cpu are you using?

Chuck



------
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]