These are chat archives for symengine/symengine

5th
Aug 2015
Isuru Fernando
@isuruf
Aug 05 2015 09:37
Isuru Fernando
@isuruf
Aug 05 2015 13:30

Do you see the warning: /usr/bin/ld: warning: libgmp.so.16, needed by /projects/b1cc51a6-c4a2-4281-98b4-a5c2b1dea21b/ext/sage-6.8-x86_64-Linux/local/lib/libmpc.so, may conflict with libgmp.so.10 ? We'll have to address that.

Python library path we are getting from the command "from distutils.sysconfig import get_config_var; print(get_config_var('LIBDIR'))" is wrong. (It's a path in the computer where sage was packaged, I think). Therefore Python library is not found

I wonder why cmake proceeds from that point. If it is fixed, then there's no problem

Ondřej Čertík
@certik
Aug 05 2015 14:08
@isuruf are you here?
Ok, I just moved it: https://github.com/symengine/symengine.spkg (next time I think there is a way for you to transfer the repository somehow)
@isuruf how do you use it to create the spkg?
Ondřej Čertík
@certik
Aug 05 2015 14:16
@isuruf here is a patch (untested): symengine/symengine.spkg#1
Isuru Fernando
@isuruf
Aug 05 2015 14:18
Compress it as a .tar.bz2 and change the extension name to .spkg
Ondřej Čertík
@certik
Aug 05 2015 14:25
@isuruf ok, would you mind documenting this in the README? Also see this: symengine/symengine.spkg#2
Isuru Fernando
@isuruf
Aug 05 2015 14:29
Btw, the spkgs are an old way of distribution, and I think they are only good for distributing packages not in the official repos. See https://groups.google.com/forum/#!topic/sage-devel/n1Y5BoVLBLw
Ondřej Čertík
@certik
Aug 05 2015 14:32
Ok. Let's not worry about travis testing for now. Do you see any further issues regarding this SPKG? If not, let's release symengine 0.1, update the spkg to use this release commit and write to the Sage mailinglist. I have to go now, but I'll be back later during the day.
Isuru Fernando
@isuruf
Aug 05 2015 14:39
Only other issue I can think of is the issue you mentioned above, where libgmp.so.10 from system is picked up because of python library not being found
Isuru Fernando
@isuruf
Aug 05 2015 16:32
@certik, yes, we should make a release first
Ondřej Čertík
@certik
Aug 05 2015 17:22
@isuruf what does the libgmp finding has to do with Python?
Isuru Fernando
@isuruf
Aug 05 2015 17:23
It's about ${LIBS} variable having PYTHON_LIBRARY_NOT_FOUND
Ondřej Čertík
@certik
Aug 05 2015 17:25
But why is that?
Isuru Fernando
@isuruf
Aug 05 2015 17:26
Python library is not found, because from distutils.sysconfig import get_config_var; print(get_config_var('LIBDIR')) returns a path from the host machine
and since ${LIBS} is corrupt, symengine links with system gmp
Ondřej Čertík
@certik
Aug 05 2015 17:30
Ah, so the problem is not with gmp, but with a corrupt LIBS, is that right?
Isuru Fernando
@isuruf
Aug 05 2015 17:30
yeah
Ondřej Čertík
@certik
Aug 05 2015 17:30
The Python finder just executes the python in path. It's weird it can't find the one from Sage, but I think we can easily fix that.
It's in $SAGE_LOCAL/bin/python, so we should probably just add this as the Python executable to use.
Isuru Fernando
@isuruf
Aug 05 2015 17:31
It does use sage's python
Ondřej Čertík
@certik
Aug 05 2015 17:31
So how can sage's python return the wrong path?
Isuru Fernando
@isuruf
Aug 05 2015 17:33
Can you take a look at Work2.term?
Output is
~/ext/sage-6.8-x86_64-Linux(master)$ ./sage -python
Python 2.7.9 (default, Jul 26 2015, 15:34:45)
[GCC 4.9.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from distutils.sysconfig import get_config_var; print(get_config_var('LIBDIR'))
/mnt/highperf/buildbot/slave/sage_git/build/local/lib
Ondřej Čertík
@certik
Aug 05 2015 17:34
I see. It's wrong.
It's the location where Sage was built the first time. But we have relocated the binary.
Isuru Fernando
@isuruf
Aug 05 2015 17:35
yeah
Ondřej Čertík
@certik
Aug 05 2015 17:35
We need to improve our CMake, so that we can tell it exactly where the Python is and where to install the modules, specified by hand on the command line.
And then we'll specify it in the spkg-install
It's just a way to figure out how to do it.
Isuru Fernando
@isuruf
Aug 05 2015 18:29
@certik, I started sage testing on travis-ci by using the same way as sympy.
How do I install the symengine directory to sage? Since sage's python directory is write-protected, I can't install symengine without a sudo. Is there an alternative to it?
Ondřej Čertík
@certik
Aug 05 2015 18:50
I would just use sudo (which slows everything down on Travis, since they use a different VM, so I would only do it on the symengine.spkg repo for this reason). Otherwise we need to install Sage from a binary tarball.
(Just like on SMC)
Isuru Fernando
@isuruf
Aug 05 2015 18:51
We could use sudo just for that job