Closed jdemeyer closed 11 years ago
Is this a specific version of OS X that causes the problem? I haven't seen this on 10.7 or 10.4.
$ ./sage -t --long -force_lib devel/sage/sage/misc/interpreter.py
sage -t --long -force_lib "devel/sage/sage/misc/interpreter.py"
[25.6 s]
----------------------------------------------------------------------
All tests passed!
Total time for all tests: 25.7 seconds
It's on OS X 10.6. I haven't determined the actual circumstances under which it occurs, but there is clearly a bug in the use of the split()
method.
Replying to @kcrisman:
Is this a specific version of OS X that causes the problem?
Perhaps relocating the Sage tree causes the failure.
You're right about that bad use of split. This doesn't happen on my 10.4 or 10.7.
This is pretty new code, in a 5.7 beta - maybe the people at that patch would know more?
I think that this is a combination of a bad use of split and Sage not relocating correctly. On my OS X 10.8.2 box, I see
sage -t "devel/sage/sage/misc/interpreter.py"
dyld: Library not loaded: /Users/palmieri/Desktop/Sage_stuff/sage_builds/clean/sage-5.7.beta1/local/lib/libgomp.1.dylib
Referenced from: /Users/palmieri/Desktop/Sage_stuff/sage_builds/sage-5.7.beta1/local/lib/R//bin/exec/R
Reason: image not found
But notice that the referenced library is supposed to be in sage_builds/clean/...
while Sage has actually been moved to sage_builds/...
.
So: the use of split should be fixed here. The rest of this is perhaps covered by #9668.
Replying to @jhpalmieri:
The rest of this is perhaps covered by #9668.
I doubt it, that seems to be a different issue.
Author: John Palmieri
Reviewer: Jeroen Demeyer
Merged: sage-5.7.beta3
This happens on some OS X installations:
The problem is that
split()
doesn't do what was intented:Component: misc
Author: John Palmieri
Reviewer: Jeroen Demeyer
Merged: sage-5.7.beta3
Issue created by migration from https://trac.sagemath.org/ticket/14042