#9896: upgrading from 4.5.3 to 4.6.alpha0 fails on OS X 10.6
--------------------------+-------------------------------------------------
Reporter: jhpalmieri | Owner: GeorgSWeber
Type: defect | Status: needs_info
Priority: blocker | Milestone: sage-4.6
Component: build | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
--------------------------+-------------------------------------------------
Comment(by jhpalmieri):
Replying to [comment:24 leif]:
> And the files in {{{.../local/lib/python2.6/site-packages/...}}} got
properly updated?!?
According to the time stamps, yes.
> Can you attach a log of the {{{./sage -b}}} run?
Which one? Here's what happens if I follow your instructions, delete
libpari-gmp.dylib, and touch complex_double.pyx:
{{{
$ ./sage -b
----------------------------------------------------------
sage: Building and installing modified Sage library files.
Installing c_lib
scons: `install' is up to date.
Updating Cython code....
Building modified file sage/rings/complex_double.pyx.
Execute 1 commands (using 1 threads)
python `which cython` --embed-positions --directive cdivision=True
-I/Applications/sage_builds/sage-4.6.alpha0-upgrade/devel/sage-main -o
sage/rings/complex_double.c sage/rings/complex_double.pyx
sage/rings/complex_double.pyx -->
/Applications/sage_builds/sage-4.6.alpha0-upgrade/local//lib/python/site-
packages//sage/rings/complex_double.pyx
Time to execute 1 commands: 4.32504701614 seconds
Finished compiling Cython code (time = 4.87559199333 seconds)
running install
running build
running build_py
running build_ext
building 'sage.rings.complex_double' extension
gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-
prototypes
-I/Applications/sage_builds/sage-4.6.alpha0-upgrade/local//include
-I/Applications/sage_builds/sage-4.6.alpha0-upgrade/local//include/csage
-I/Applications/sage_builds/sage-4.6.alpha0-upgrade/devel//sage/sage/ext
-I/Applications/sage_builds/sage-4.6.alpha0-upgrade/local/include/python2.6
-c sage/rings/complex_double.c -o
build/temp.macosx-10.6-i386-2.6/sage/rings/complex_double.o -std=c99
-D_XPG6 -w
gcc -L/Applications/sage_builds/sage-4.5.3/local/lib -bundle -undefined
dynamic_lookup build/temp.macosx-10.6-i386-2.6/sage/rings/complex_double.o
-L/Applications/sage_builds/sage-4.6.alpha0-upgrade/local//lib -lcsage
-lgsl -lcblas -latlas -lpari -lgmp -lm -lstdc++ -lntl -o
build/lib.macosx-10.6-i386-2.6/sage/rings/complex_double.so
Total time spent compiling C/C++ extensions: 7.72538805008 seconds.
running install_lib
copying build/lib.macosx-10.6-i386-2.6/sage/rings/complex_double.so ->
/Applications/sage_builds/sage-4.6.alpha0-upgrade/local/lib/python2.6
/site-packages/sage/rings
running install_egg_info
Removing
/Applications/sage_builds/sage-4.6.alpha0-upgrade/local/lib/python2.6
/site-packages/sage-0.0.0-py2.6.egg-info
Writing
/Applications/sage_builds/sage-4.6.alpha0-upgrade/local/lib/python2.6
/site-packages/sage-0.0.0-py2.6.egg-info
real 0m13.963s
user 0m12.678s
sys 0m1.095s
}}}
> The only (other) thing I could imagine is some old PARI library in the
linker/loader search path ''during linking'', but not at run-time (i.e.
dynamic loader search path). (Really) Environment issue?
Well, I see it on two different machines. I don't have LD_LIBRARY_PATH or
DYLD_LIBRARY_PATH set, and when I run "./sage -sh", I don't see anything
odd in those variables. I've posted what I get from "export" ordinarily
and also after running "./sage -sh" at
[http://sage.math.washington.edu/home/palmieri/misc/env.txt]. I'm going
to try this all on bsd.math, which involves building sage 4.5.3 first, so
it will take a while. I've hardly used that machine, so my environment
there is pretty vanilla.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9896#comment:25>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
