This is the mail archive of the
mailing list for the binutils project.
Re: Change default location of DJGPP's ld scripts
- To: email@example.com
- Subject: Re: Change default location of DJGPP's ld scripts
- From: "Mark E." <firstname.lastname@example.org>
- Date: Thu, 9 Sep 1999 22:47:17 -0400
- References: <199909100029.AAA17468@out4.ibm.net> (email@example.com)
> 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
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:
they are instead in instead:
truncating the target alias in the same way as gcc for the ldscripts directory would
which will work. But it kinda looks as if someone made a mistake and put in an extra
/djgpp in the path.
Mark Elbrecht, firstname.lastname@example.org