RE: [avr-libc-dev] Re: AVR-libc-dev Digest, Vol 40, Issue 3

[Eric Weddington]

> -----Original Message-----
> From: 
> address@hidden 
> [mailto:address@hidden
> org] On Behalf Of David Breeze
> Sent: Thursday, September 14, 2006 3:44 AM
> To: address@hidden; address@hidden
> Subject: [avr-libc-dev] Re: AVR-libc-dev Digest, Vol 40, Issue 3
> 
> 
> 
> 
> >Btw., does anyone know why there are five linker scripts per
> >device/architecture?  (.x, .xbn, .xn, .xr, .xu)
> --
> cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL
> 
> I asked the same question about 4 years ago.  The answer I 
> got then, from Peter Jansen, was
> 
> "from the binutils/ld/genscripts.sh source,
> 
> #Generate 5 or 6 script files from a master script template in
> #$(srcdir)/scripttempl/${SCRIPT_NAME}.sh.  Which one of the 5 or 6
> #script files is actually used depends on command line options given
> #to ld.  (SCRIPT_NAMES was set in the emulparams_file)
> #
> #A .x script file is the default script
> #A .xr script is for linking without relocation (-r flag)
> #A .xu script is like .xr but *do* create constructors (-Ur flag)
> #A .xn script is for linking with -n flag (mix text and data 
> on same page).
> #A .xbn script is for linking with -N flag (mix text and data 
> on same page).
> #A .xs script is for generating a shared library with the 
> --shared flag; 
> #it is only generated if $GENERATE_SHLIB_SCRIPT is set by the 
> emulation parameters"

Thanks for bringing this up David! I've now committed this info to the
avr-libc FAQ in the user manual.

Eric