public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: "Mark E." <snowball3@bigfoot.com>
Cc: binutils@sourceware.cygnus.com
Subject: Re: Change default location of DJGPP's ld scripts
Date: Fri, 10 Sep 1999 01:21:00 -0000	[thread overview]
Message-ID: <jepuzrnppv.fsf@hawking.suse.de> (raw)
In-Reply-To: <199909100247.CAA13892@out2.ibm.net>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]

"Mark E." <snowball3@bigfoot.com> writes:

|> 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.

c:/djpgg seems to be ${prefix}, and tooldir is ${prefix}/${target_alias},
where ${target_alias} can be anything that is accepted by config.sub.  So
it's a matter of how you call configure what you get here.  Just pass the
appropriate --target name that fits into the ridiculous DOS file name
rules.

Andreas.

-- 
Andreas Schwab                                  "And now for something
schwab@suse.de                                   completely different."
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg

      reply	other threads:[~1999-09-10  1:21 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.
1999-09-10  1:21     ` Andreas Schwab [this message]

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=jepuzrnppv.fsf@hawking.suse.de \
    --to=schwab@suse.de \
    --cc=binutils@sourceware.cygnus.com \
    --cc=snowball3@bigfoot.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).