public inbox for bfd@sourceware.org
 help / color / mirror / Atom feed
From: Carlo Wood <carlo@runaway.xs4all.nl>
To: bje@cygnus.com (Ben Elliston)
Cc: bothner@cygnus.com, hjl@gnu.org, carlo@runaway.xs4all.nl,
	gas2@cygnus.com, bfd@cygnus.com, dkl@redhat.com
Subject: Re: [cygnus.gas2] binutils bug: config.guess
Date: Mon, 05 Apr 1999 08:12:00 -0000	[thread overview]
Message-ID: <199904051358.PAA02063@jolan.ppro> (raw)
In-Reply-To: <Pine.LNX.3.95.990405162904.6486A-100000@moshpit.cygnus.com>

| > Or just do:
| > 	(cd /; ld)
| > Remember: (CMD) runs CMD in a sub-shell.
| 
| Silly me.  Thanks,
| 
| Ben

I'd suggest to do that where you detect the path to ld:

	ld_exec=`(cd /; which ld)`

After all, the problem is in `which', not in the normal
shell search.

[ proof:

~/tmp>ls -ld ld
drwxr-xr-x   2 carlo    users        1024 Apr  5 15:55 ld/
~/tmp>ld -V
GNU ld version 2.9.1 (with BFD 2.9.1.0.15)
  Supported emulations:
   elf_i386
   i386linux

]

I already mailed to Ben, I intend to rewrite `which' so
it behaves the same as the shell search (ie, will skip
directories).

I suppose that

    if (!access(test, X_OK) && !stat(test, &m))
      found = S_ISREG(m.st_mode);

will do?

[ Now it just does the access(test, X_OK) ].

I suppose the main problem will be to get
everyone to upgrade their `which' ;).

-- 
 Carlo Wood  <carlo@runaway.xs4all.nl>

PS dkl@redhat.com : reference, bug #1998

  reply	other threads:[~1999-04-05  8: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
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 [this message]
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=199904051358.PAA02063@jolan.ppro \
    --to=carlo@runaway.xs4all.nl \
    --cc=bfd@cygnus.com \
    --cc=bje@cygnus.com \
    --cc=bothner@cygnus.com \
    --cc=dkl@redhat.com \
    --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).