Good catch, yes, this fixes the weirdness on python2! On Friday, January 26, 2018 at 3:59:28 PM UTC, Erik Bray wrote: > > On Fri, Jan 26, 2018 at 11:51 AM, Dima Pasechnik <dim...@gmail.com > <javascript:>> wrote: > > It appears that libpython is not correctly linked to the python3 > executable: > > ... > > > > make[2]: Leaving directory > > > '/var/export/home/dima/Sage/sagetrac-mirror/local/var/tmp/sage/build/python3-3.6.1.p1/src' > > > > Testing importing of various modules... > > ld.so.1: python: fatal: libpython3.6m.so.1.0: open failed: No such file > or > > directory > > ./spkg-build: line 155: 22938 Killed $PYTHON -c "import > > $module" > > > > ... > > see http://users.ox.ac.uk/~coml0531/tmp/python3-3.6.1.p1.log > > and http://users.ox.ac.uk/~coml0531/tmp/config3.log > > > > > -------------------------------------------------------------------------------------------- > > > > > > More weirdly, building of python2 ends with > > local/var/tmp/sage/build/python2-2.7.14.p2/src/python > > being (almost) a copy of systemwide (sic!) python2: > > You probably need to put in something like this: > > > https://git.sagemath.org/sage.git/tree/build/pkgs/python3/spkg-build?h=develop#n98 > > > but for SunOS. I think at the time I wrote that I had assumed we were > no longer supporting SunOS. But assuming that LD_LIBRARY_PATH works > the same as on Linux then maybe that "$UNAME = "Linux" clause should > just be the default (with DYLD_LIBRARY_PATH on OSX, and on Cygwin no > variables need to be set). > > Best, > Erik >
-- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
