From: Ben Elliston <bje@cygnus.com>
To: hjl@gnu.org, carlo@runaway.xs4all.nl
Cc: gas2@cygnus.com, bfd@cygnus.com
Subject: Re: [cygnus.gas2] binutils bug: config.guess
Date: Sun, 04 Apr 1999 20:12:00 -0000 [thread overview]
Message-ID: <Pine.LNX.3.95.990405125857.5800B-100000@moshpit.cygnus.com> (raw)
In-Reply-To: <877lsq2xp2.fsf@cygnus.com>
I wasn't entirely sure where I should send this, as it seems to be
specific to binutils. It's a response to Carlo Wood's bug report about
config.guess in the binutils package:
> From: Carlo Wood <carlo@runaway.xs4all.nl>
> Message-Id: <199903091509.QAA03972@jolan.ppro>
> Subject: binutils bug: config.guess
> when trying to compile binutils-2.9.1.0.22b, I ran into a problem with
> config.guess.
> I have "." in my PATH, and it seems that makes config.guess fail to
> execute `ld'. It tries to execute the directory ld/ in binutils.
> I know I shouldn't have a "." in my path before /usr/bin, but I am sure
> I am not the only one that has it any way :).
This is quite a specific case that causes this to fail. Since it only
occurs when there is a subdirectory named `ld' (as there is in binutils)
and then only when you have `.' in front of the path to your ld program, I
am inclined to suggest a binutils-only modification to config.guess that
just warns:
if test -d `which ld`
echo "Error: cannot invoke ld"
fi
.. or something to that effect. I don't think I am prepared to hack up
config.guess to cater for this, unless someone has a more elegant
solution.
> While you're at it, I found another problem with config.guess a while
> ago: I can imagine that someone doesn't have a 'cc', but only a 'gcc'.
> If you don't set CC in that case, config.guess also fails, a bit weird
> (and confusing) for a GNU package.
I feel this is a valid complaint; I will put it onto the heap. Thanks,
Ben
next parent reply other threads:[~1999-04-04 20:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877lsq2xp2.fsf@cygnus.com>
1999-04-04 20:12 ` Ben Elliston [this message]
1999-04-04 22:53 ` Per Bothner
1999-04-04 22:58 ` Ben Elliston
1999-04-04 23:25 ` Per Bothner
1999-04-04 23:30 ` Ben Elliston
1999-04-05 8:12 ` Carlo Wood
1999-04-06 2:13 ` Richard Stallman
1999-04-06 9:10 ` Carlo Wood
1999-04-05 3:18 ` Ben Elliston
1999-04-05 6:35 ` Jim Meyering
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=Pine.LNX.3.95.990405125857.5800B-100000@moshpit.cygnus.com \
--to=bje@cygnus.com \
--cc=bfd@cygnus.com \
--cc=carlo@runaway.xs4all.nl \
--cc=gas2@cygnus.com \
--cc=hjl@gnu.org \
/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).