The definition of "relative path" in the ghc-conf error message ignores a lot of the complexities of Windows which has both a current drive and current directories for each drive. If the meaning is to be "non-absolute", then what about UNC pathnames of the form \partition\xx\yyy No, it does not ignore any complexities. UNC pathnames are detected as absolute and your example is wrong. They start with two slashes: "\\partition\xx\yyy". What about the passthru pathnames starting with \?\ which are entirely...
The definition of "relative path" in the ghc-conf error message ignores a lot of the complexities of Windows which has both a current drive and current directories for each drive. If the meaning is to be "non-absolute", then what about UNC pathnames of the form \partition\xx\yyy No, it does not ignore any complexities. UNC pathnames are detected as absolute and your example is wrong. They start with two slashes: "\partition\xx\yyy". What about the passthru pathnames starting with \?\ which are entirely...
build failure with gcc-5
sci-libs/libspatialindex: add myself to metadat...
sci-libs/libspatialindex: version bump to 1.8.5
sci-libs/libspatialindex: rm old 1.6.1
fix --enable-tiff switch
That doesn't work for me, still the same build failure.