On 09/23/2014 12:23 PM, Clemens Heuberger wrote:
My $HOME/.sage is a symbolic link with a trailing slash:
~ $ ls -ld .sage
lrwxrwxrwx 1 cheuberg lsci 11 Sep 23 10:25 .sage -> /tmp/.sage/
When running make ptestlong (sage 6.4.beta3) with this configuration, I get
quite a number of failing doctests (see below for details) and several files are
created or overwritten (see below for details).
I'm not sure if this observation helps or is related, but I too was once
struck by a leading slash problem:
http://trac.sagemath.org/ticket/14018
My solution[*] was to change the link from "/whatever" to "///whatever":
I'd be curious to know if this "fix" also works for you.
HTH,
Christian
[*] this is based on this quote from IEEE Std 1003.1, 2004 Edition:
A pathname consisting of a single slash shall resolve to the root
directory of the process. A null pathname shall not be successfully
resolved. A pathname that begins with two successive slashes may be
interpreted in an implementation-defined manner, although more than
two leading slashes shall be treated as a single slash.
http://pubs.opengroup.org/onlinepubs/000095399/basedefs/xbd_chap04.html#tag_04_11
Somewhere my "/whatever" became "//whatever" and that, being
"implementation defined" was no longer recognized as "/whatever".
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
