[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
The following reply was made to PR pkg/43550; it has been noted by GNATS.
From: David Holland <dholland-pbugs%netbsd.org@localhost>
Subject: Re: pkg/43550
Date: Wed, 13 Oct 2010 08:45:04 +0000
On Wed, Oct 13, 2010 at 12:50:04AM +0000, John D. Baker wrote:
> Because my symlink was relative, it failed. I re-linked "/d0" to an
> absolute path of "/Volumes/d0" and it built and installed just fine.
That seems odd. The usual problem with symlinks is that the wrappers
rely on textual equality of pathnames and build systems that do things
like "cd $FOO && pwd" end up using different paths that don't match.
But absolute vs. relative symlinks should be invisible... although
maybe MacOS is doing something weird and/or something is tripping on
the weird ksh symlink-crossing behavior.
> Now I wonder how many of my other problems with pkgsrc on MacOS X might
> have been caused by the same thing...
Quite a few, I bet. When the wrappers go kablooey everything fails in
really strange ways.
David A. Holland
Main Index |
Thread Index |