[Top][All Lists]

[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: Wed, 24 Jul 2002 19:57:35 -0500
User-agent: Mutt/1.2.5i

On Wed Jul 24 02:03 2002 -0700, Paul Eggert wrote:
> OK, now I understand the problem.  I also see that the problem occurs
> even in absolute path names.  For example, with /bin/ksh on Solaris 8:
> 33-sic $ ls -ld /tmp/usr/local/src/dummy-0.1/../../common
> drwxrwxr-x   3 eggert   eggert       183 Jul 24 01:54 
> /tmp/usr/local/src/dummy-0.1/../../common
> 34-sic $ cd /tmp/usr/local/src/dummy-0.1/../../common
> /bin/ksh: /tmp/usr/local/src/dummy-0.1/../../common:  not found
> What a botch!

Exactly. ;/

> No, mine uses /bin/bash and not /bin/ksh.  This probably explains it.
> You don't have the SUNWbash package installed, so you don't have
> /bin/bash.

Yeah, that explains the difference.

> However, I still don't like the solution of invoking /bin/pwd first,
> for the reasons I mentioned earlier.  Why can't we fall back on
> /bin/pwd only if the current method fails?  That way, only the poor
> ksh users will be stuck with the problems of ugly names and/or
> /bin/pwd failing.

Sounds reasonable.  Please look over the attached patch and let me
know what you think.  If it looks good, I'll commit it.


Mark D. Roth <address@hidden>

Attachment: autoconf-pwd-symlink-fix-2.diff
Description: Text document

reply via email to

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