This is the mail archive of the binutils@sourceware.cygnus.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Change default location of DJGPP's ld scripts


> use its internal linker script, it does so.  It only uses the external
> linker script if there is no appropriate internal script.  That is,
> the linker never falls back to the internal linker script.  The fall
> back is the other way around.

Then I misunderstood how this worked.

> We don't put target_alias in the tooldir path because we expect
> everybody to build their own binutils.  I'm not sure what you mean by
> that.

The statement was based on the above misunderstanding. Forget about it.

> I don't see why removing target_alias is the answer.  The answer would
> seem to be using something which DOS can cope with.  Perhaps on DOS we
> should simply truncate the name.
> 
> gcc uses target_alias when it finds programs like the assembler and
> linker.  gcc and the binutils cooperate in that regard.  Does this
> work on DOS?  Perhaps people are simply required to put those programs
> on their PATH.

What happens with gcc is the target_alias is truncated to 'djgpp', so instead of the 
egcs 1.12 backends (cc1.exe, etc.) being in:
c:/djgpp/lib/gcc-lib/i386-pc-msdosdjgpp/egcs-291.66/

they are instead in instead:
c:/djgpp/lib/gcc-lib/djgpp/egcs-291.66/

truncating the target alias in the same way as gcc for the ldscripts directory would 
be:
c:/djgpp/djgpp/lib/ldscripts/

which will work. But it kinda looks as if someone made a mistake and put in an extra 
/djgpp in the path.


--- 
Mark Elbrecht, snowball3@bigfoot.com
http://snowball.frogspace.net/

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]