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

[Allan Clark <allanc at chickenandporn dot com>]

Chuck Meade wrote:
> Hi Pramod,
>
>   
> > > Question to the original poster -- what is the binary format of your >a.out
> > > file?  If it truly is in a.out format, then was your kernel
> > >       
> > configured to >handle
> >     
> > > the a.out binary format?
> > >       
> > Its ELF .
> > Yeah... sure, coz I can run the a.out of the same program; compiled
> > using the existing (old) GCC in the TARGET.
> >     
>
> I verified that those are indeed elf ARM binaries.  However they are built
> with a toolset that is compatible with Linux 2.4.3 -- quite old tools.
> See the output when I run "file" on the files you sent:
>
> # file arm*
> arm-9tdmi-linux-gnu-hello:        ELF 32-bit LSB executable, ARM, version 1 (ARM), for GNU/Linux 2.4.3, dynamically linked (uses
> shared libs), not stripped
> arm-9tdmi-linux-gnu-hello-static: ELF 32-bit LSB executable, ARM, version 1 (ARM), for GNU/Linux 2.4.3, statically linked, not
> stripped
>
> Note the "for GNU/Linux 2.4.3".  Check your working a.out file the same
> way (use the file command on it).  I bet you will see a substantially
> different version number than 2.4.3.  Considering that that kernel
> is from March 2001, you can bet that a lot has changed since then in
> the kernel, in gcc, glibc, and binutils.
"2.4.3" refers to "minimum linux that it will run on".  I used to see a 
lot of 2.0.0 for no reason.  making it match more closely should only 
reduce redundant code for kernels you'll never use, but it shouldn't be 
setting the kernel version exactly.  It's just a minimum, as far as I know.

Allan

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com