From: "Mark E." <snowball3@bigfoot.com>
To: binutils@sourceware.cygnus.com
Subject: Re: Change default location of DJGPP's ld scripts
Date: Thu, 09 Sep 1999 19:48:00 -0000 [thread overview]
Message-ID: <199909100247.CAA13892@out2.ibm.net> (raw)
In-Reply-To: <19990910021116.8914.qmail@daffy.airs.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
> 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/
next prev parent reply other threads:[~1999-09-09 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-09 17:31 Mark E.
1999-09-09 19:12 ` Ian Lance Taylor
1999-09-09 19:48 ` Mark E. [this message]
1999-09-10 1:21 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199909100247.CAA13892@out2.ibm.net \
--to=snowball3@bigfoot.com \
--cc=binutils@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).