Christian Lynbech <christian@...> writes:
> The machine is a Mac PPC with OSX and the error listed below is
> encountered both with sbcl 1.0.10 and 1.0.11. The compiler used is SBCL
> and I have tried both the 1.0.2 version as found on the SBCL homepage
> and 1.0.11 as compiled by myself.
> 10: (SB-INT:UNIX-NAMESTRING
SBCL doesn't like that pathname, since it's parsed as (:ABSOLUTE :UP
"usr" ...), which the CL standard explicitly defines as needing to
signal an error (as usual... not only are pathnames so underspecified
as to be useless, but also overspecified in strategic places to
I'm tempted to just remove the check forbidding :ABSOLUTE :UP, since
as far as I can see the only benefit is slavishly obeying the letter
of the spec. (:ABSOLUTE "foo" :UP :UP ...) is still allowed, so it's
not like we're shielding the users from the root directory being its
own parent in Unix filesystems.
Incidentally, truename needs to know about .. in the root directory too:
(truename "/etc/../../") => #P"/../"
> 11: (FIND-EXECUTABLE-IN-SEARCH-PATH
If you want an immediate solution, you should be able to build SBCL by
trimming down that PATH a bit for the build, or by fixing the symlink
(presumably /usr/texbin) that expands to /../usr/local/texlive/... to
point to /usr/local/texlive/... instead.