On 15 June 2010 06:48, Dan Drake <dr...@kaist.edu> wrote: > Hello, > > I'm trying to test some patches and I want to try them on t2. I > downloaded a binary [1], untarred it, and started it -- and it failed:
1) Can you try this binary /usr/local/sage-4.3.0.1-Solaris-10-SPARC-sun4u-or-sun4v.tar.gz It is old, but I built it in a way that it would run with the least effort. I included the runtime libraries that are needed, but which do not included when runs 'sage -bdist'. That binary was not built on 't2'. 2) Minh created that binary you have. I would hope that adding the following to your LD_LIBRARY_PATH /usr/local/gcc-4.4.1-sun-linker/lib:/usr/local/gcc-4.4.1-sun-linker/lib/sparcv9:/usr/local/lib would allow that to work. With the binary I refereed to above, that should be unnecessary. i.e run $ LD_LIBRARY_PATH=/usr/local/gcc-4.4.1-sun-linker/lib:/usr/local/gcc-4.4.1-sun-linker/lib/sparcv9:/usr/local/lib $ export LD_LIBRARY_PATH > > ImportError: ld.so.1: python: fatal: relocation error: file > /disk/scratch/drake/t2/sage-4.4.2-t2.math/local/lib//libgmpxx.so.3: symbol > _ZNKSt5ctypeIcE13_M_widen_initEv: referenced symbol not found > Error importing ipy_profile_sage - perhaps you should run %upgrade? > WARNING: Loading of ipy_profile_sage failed. I must admit, I find that a bit od, but try the LD_LIBRARY_PATH like I said. I don't think binaries for t2 should be considered suitable for redistribution until they have been tested on 't2' in a zone, which lacks the tools which t2 has. > I tried with a binary for 4.4, and got the same error. This seems > worrisome, as I'm using a binary that was built on t2! Do I need to set > some environment variables to get this to work? Is there a guide to > running Sage on t2 that I've missed? http://wiki.sagemath.org/solaris-binaries has some links. http://wiki.sagemath.org/devel/Building-Sage-on-the-T5240-t2 describes how to build from source on t2. > It would be useful if downloading a binary and running it on t2 was as > easy as possible, so that more people test patches and updates there. Yes agreed. I think the trick to that is to include the runtime libraries that are not included when 'sage -bdist' is run. Either that, or we distribute two files - one the runtime libraries, the other the rest of Sage. > Thanks, > > Dan 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
