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]

RE: ELF_DYNAMIC_INTERPRETER


But say if my application requires the 'arm-linux-gcc' and the
'arm-linux-ld' to be invoked separately, then isn't it the better way out?

> -----Original Message-----
> From: Phil Blundell [mailto:pb@nexus.co.uk]
> Sent: Friday, November 21, 2003 7:38 PM
> To: Manoj Verma, Noida
> Cc: crossgcc@sources.redhat.com; Kai Ruottu; karuottu@mbnet.fi
> Subject: Re: ELF_DYNAMIC_INTERPRETER
> 
> 
> on Fri, Nov 21, 2003 at 07:29:44PM +0530, Manoj Verma, Noida wrote:
> > This is causing the dynamic interpreter of my executable as
> > "/usr/lib/ld.so.1" when I link my program using arm-linux-ld.
> 
> "Don't do that, then".
> 
> It would be a better idea to call arm-linux-gcc for linking; it will
> pass the appropriate --dynamic-linker option to ld.
> 
> elf32-arm.h is not a Linux-specific file, and it wouldn't 
> make sense to
> hard-wire the Linux program interpreter in there.
> 
> p.
> 
> ------
> Want more information?  See the CrossGCC FAQ, 
> http://www.objsw.com/CrossGCC/
> Want to unsubscribe? Send a note to 
> crossgcc-unsubscribe@sources.redhat.com
> 

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