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] | |
> -----Original Message-----
> From: Kai Ruottu [mailto:kai.ruottu@luukku.com]
> Sent: Tuesday, February 12, 2002 4:19 PM
> To: Wolfgang Fritz
> Cc: crossgcc@sources.redhat.com
> Subject: Re: Can't build gcc-2.95.3 with g++ for m68k-elf
>
>
> Wolfgang Fritz wrote:
> >
> > For my "real life" applications I have one problem that I
> couldn't solve
> > up to now. I have one application which needs a special
> linker script
> > which is conflicting with the default linker script from
> the specs file.
> > I have the following entry in the specs file:
> >
> > *link:
> > %{!T:-T dt.ld%s}
> >
I got that from a configuration file in the gcc-2.95.3 gcc/config
directory (don't remember what target)
> > which LOOKS to me as it would mean "If there are no -T
> options on the
> > linker command line, use the default dt.ld, otherwise
> don't". That is
> > what I want. But dt.ld is always used, and my special
> application gives
> > nice error messages during the link.
>
> The 'specs' file will be read by 'gcc', not by 'ld', so the
> logic goes:
> "If there are no -T options on the gcc command line, put the
> option '-T dt.ld%s'
> onto the 'ld' command line, otherwise don't"... But 'gcc'
> wouldn't understand
> the '-T' option because it is a option for 'ld'... So the
> right way is to put :
>
> *link:
> %{!Wl,-T*:-T dt.ld%s}
>
That sounds logical, but it does not work :-( It is the same as before:
dt.ld is always used, and I get an linker error like "cannot move
location counter backwards".
I tried some other variations of that spec like
%{!Wl,-T:-T dt.ld%s}
%{!Wl*:-T dt.ld%s}
but they didn't work either.
Up to now I have not found any docs about spec file syntax, and I think
I have to find the location of the spec file processing in the gcc
sources :-(
Wolfgang
> there, because the linker options are given using the
> '-Wl,<ld_options>'
> on the 'gcc' command line...
>
> Cheers, Kai
>
>
>
> >
> > I could not find documentation about the specs entries (I'll keep on
> > searching). Is ther a solution for this problem which I
> would imagine is
> > a common one in embedded systems with differing memory layouts etc.
> >
> > Wolfgang
> >
> > > Regards, Kai
> > >
> > > ------
> > > 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
------
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] |