*** Floating Point Unavailable ***
Fri Jul 2 04:44:00 GMT 1999
"C. M. Heard/VVNET, Inc." wrote:
> On Thu, 1 Jul 1999, Scott Howard wrote:
> > C. M. Heard/VVNET, Inc. wrote:
> [ ... ]
> > > With older versions (2.7.2 et. seq) of gcc it was possible (at least when
> > > using gnu-ld) to organize things any way you wanted by writing a linker
> > > directive file to replace the one that gcc uses by default. Granted, most
> > > of my experience is with MIPS, but I recall doing similar stuff with ppc
> > > about two years ago. Is this not still possible?
> > On the PowerPC port there are a several files which are automatically
> > linked in, for startup support and also for ELF constructor/destructor
> > support. This stuff gets put on the linker command line, so the linker
> > script file can't prevent these files from being included into the final
> > program.
> > Most of this is done in the 'specs' file, so strictly speaking this
> > behaviour could be changed just by editing the specs file. However, I
> > don't believe changing the specs file would be a good idea, since it
> > will change the compiler's 'default' behaviour; the simplest solution is
> > to add a couple of assembly instructions to the application program.
-T is used to specify the command file (linker script to use).
-specs is used to specify the specs file to use.
Copy the defaults to an appropriate place in your source tree, edit them to your
liking and then use the -T and -specs arguments to point to your own versions.
New CrossGCC FAQ: http://www.objsw.com/CrossGCC
To remove yourself from the crossgcc list, send
mail to email@example.com with the
text 'unsubscribe' (without the quotes) in the
body of the message.
More information about the crossgcc