autoconf-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem with symlinks and VPATH Builds


From: Mark D. Roth
Subject: Re: Problem with symlinks and VPATH Builds
Date: Sun, 21 Jul 2002 13:08:51 -0500
User-agent: Mutt/1.2.5i

On Sun Jul 21 00:17 2002 -0700, Paul Eggert wrote:
>   * Sometimes /bin/pwd fails when plain pwd would succeed.  Here's
>     a contrived example:
> 
>         $ cd /tmp
>         $ mkdir -p d/e
>         $ cd d/e
>         $ chmod 0 /tmp/d
>         $ pwd
>         /tmp/d/e
>         $ /bin/pwd
>         pwd: cannot determine current directory!

Good point.  We might be able to compensate for this by trying
/bin/pwd, but only using the result if it exists successfully.  I know
that's not ideal, but I can't think of anything better.  If you have
any other suggestions, I'd love to hear them.


> I went back to your original message
> <http://mail.gnu.org/pipermail/autoconf/2002-July/013682.html>
> and I could not reproduce the problem with autoconf 2.53 and Solaris 8
> sparc, so I think there may be something else going on here.  Perhaps
> the bug is somewhere else, and is not in Autoconf.
> 
> Here's how I tried to reproduce the problem.  I created the following
> shell script and called it "/tmp/doit":
[...]
> I then ran "sh -x /tmp/doit", with the following results:

Try "ksh -x /tmp/doit".  The problem doesn't occur with sh, since it
doesn't set $PWD.

-- 
Mark D. Roth <address@hidden>
http://www.feep.net/~roth/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]