From: Jeffrey A Law <law@hurl.cygnus.com>
To: manfred@s-direktnet.de, Manfred.Hollstein@ks.sel.alcatel.de
Cc: oliva@dcc.unicamp.br, egcs@egcs.cygnus.com
Subject: Re: $tooldir
Date: Sun, 31 Jan 1999 23:58:00 -0000 [thread overview]
Message-ID: <1145.916849521@hurl.cygnus.com> (raw)
In-Reply-To: <13989.52523.298092.823253@sls5gj.stgl.sel.alcatel.de>
In message < 13989.52523.298092.823253@sls5gj.stgl.sel.alcatel.de >you write:
> On nil, 20 January 1999, 10:16:36, oliva@dcc.unicamp.br wrote:
>
> > On Jan 20, 1999, Manfred Hollstein <manfred@s-direktnet.de> wrote:
> >
> > >> So I came up with the following idea: if any -Bdir argument is given,
> > >> gcc would search for as and ld in those directories before trying to
> > >> use the hard-coded pathnames.
> >
> > > IMO, that's a good idea. But, shouldn't we (the collect2 program)
> > > then treat "nm", "strip" (probably other programs) in a similar fashio
> n?
> >
> > Don't we? I mean, do we currently hardcode the full pathnames of nm
> > and strip in collect2?
>
> Oops, I just looked at the code in collect2.c. Both programs (like "ldd"
> and others, too) are looked for using an extended search mechanism. If
> "gcc" knows where its ${libsubdir} is, what its ${target_alias} is, it'll
> pass some environment variables to collect2 initialized from those values.
> Hence, it should work with "nm" and "strip", too.
>
> Forget about my complaint.
It's still a valid complaint in the sense that we want to be able to move the
whole toolchain and have collect2 do the right thing automatically. That's
the follow-on patch once we get $tooldir sorted out. :-) But we can't really
go anywhere until $tooldir is fixed.
jeff
next prev parent reply other threads:[~1999-01-31 23:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-31 23:58 $tooldir Jeffrey A Law
1999-01-31 23:58 ` $tooldir Alexandre Oliva
1999-01-26 7:17 ` $tooldir Jeffrey A Law
1999-01-26 10:26 ` $tooldir Alexandre Oliva
1999-01-26 10:58 ` $tooldir Donn Terry
1999-01-31 23:58 ` $tooldir Donn Terry
1999-01-31 20:13 ` $tooldir Jeffrey A Law
1999-02-01 1:09 ` $tooldir Alexandre Oliva
[not found] ` < ork8y2cx7d.fsf@araguaia.dcc.unicamp.br >
1999-02-01 9:11 ` $tooldir Jeffrey A Law
1999-02-01 9:16 ` $tooldir Alexandre Oliva
1999-02-28 22:53 ` $tooldir Alexandre Oliva
1999-02-28 22:53 ` $tooldir Jeffrey A Law
1999-02-28 22:53 ` $tooldir Alexandre Oliva
1999-01-31 23:58 ` $tooldir Alexandre Oliva
1999-01-31 23:58 ` $tooldir Jeffrey A Law
1999-01-31 23:58 ` $tooldir Manfred Hollstein
1999-01-31 23:58 ` $tooldir Alexandre Oliva
1999-01-31 23:58 ` $tooldir Manfred Hollstein
1999-01-31 23:58 ` Jeffrey A Law [this message]
1999-01-31 23:58 ` $tooldir Bill Currie
1999-01-31 23:58 ` $tooldir Jeffrey A Law
1999-01-20 17:37 ` $tooldir Bill Currie
1999-01-20 23:28 ` $tooldir Jeffrey A Law
1999-01-31 23:58 ` $tooldir Jeffrey A Law
1999-01-31 23:58 ` $tooldir Bill Currie
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=1145.916849521@hurl.cygnus.com \
--to=law@hurl.cygnus.com \
--cc=Manfred.Hollstein@ks.sel.alcatel.de \
--cc=egcs@egcs.cygnus.com \
--cc=manfred@s-direktnet.de \
--cc=oliva@dcc.unicamp.br \
/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).