On 21 Feb, 05:16, Alex Ghitza <aghi...@gmail.com> wrote: > Hi, > > This question is probably addressed to David Kirkby and Minh Van Nguyen, > but I'm posting it here so others may profit. > > I'm trying my best to be a good citizen and test a new spkg and some > patches on Solaris, more precisely on t2. I could not use the binary > posted by Minh so I downloaded the one built by David from one of the > mirrors. It works fine, and installing the new spkg also went well. > I'm stuck at trying out a patch: > > [ghi...@t2 sage-4.3.0.1-Solaris-10-SPARC-sun4u-or-sun4v]$ cd devel/sage/sage > [ghi...@t2 sage]$ hg qimport ~/pslq.patch > abort: couldn't find mercurial libraries in [/usr/local/bin > /usr/lib/python24.zip /usr/lib/python2.4 /usr/lib/python2.4/plat-sunos5 > /usr/lib/python2.4/lib-tk /usr/lib/python2.4/lib-dynload > /usr/lib/python2.4/site-packages /usr/lib/python2.4/vendor-packages] > (check your install and PYTHONPATH) > [ghi...@t2 sage]$ which hg > /usr/local/bin/hg > > I would therefore imagine that the libraries in question should be under > /usr/local/lib/, but I couldn't manage to get this to work. > > It would be great if someone with admin superpowers on t2 got this fixed > globally, since having the mercurial binaries but not the libraries is > not working so well. > > Best, > Alex > > -- > Alex Ghitza --http://aghitza.org/ > Lecturer in Mathematics -- The University of Melbourne -- Australia
export PYTHONPATH=/usr/local/lib/python2.4/site-packages will allow the system wide 'hg' to work. I'd be interested why you could not use the binary posted by Minh, but you could use the one I made. Minh made that on t2, whereas I created the binary on an old low-end Sun Netra T1 running Solaris 10 03/2005, which was the first release of Solaris 10. Had you taken the two binaries and tried to run them on another machine running an older release of Solaris 10, then I would have expected Minh's to fail and mine work. But since Minh's binary was built on t2, it should work on t2. I suspect the issue could be that Minh has his LD_LIBRARY_PATH to point to the location of the gcc C, C++ and Fortran libraries. Unless yours is set simularly, then the sage binary might fail to find the GNU libraries. In contrast, I copiled the libraries into $SAGE_ROOT/local/bin/libs, so that my binary does not require that gcc be installed on a system or if it installed, does not require that Sage know of its location. Anyway, whatever the reason, I'm sure Minh and I would like to resolve why one binary works, but the other does not. Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
