I've just created an spkg-check file for pynac, so it runs the test suite. But
if it does check anything, it is not exactly making it clear what it is
checking. I'm left wondering what, if anything is tested. Whatever is tested
takes next to no time to test, so it does not look like its a very extensive
test suite.
Done installing pynac.
real 0m40.374s
user 0m34.001s
sys 0m4.877s
Successfully installed pynac-0.2.0.p4
Running the test suite.
Testing a 64-bit version of pynac
Making check in ginac
make[1]: Entering directory
`/export/home/drkirkby/sage-4.5.alpha0/spkg/build/pynac-0.2.0.p4/src/ginac'
make[1]: Nothing to be done for `check'.
make[1]: Leaving directory
`/export/home/drkirkby/sage-4.5.alpha0/spkg/build/pynac-0.2.0.p4/src/ginac'
make[1]: Entering directory
`/export/home/drkirkby/sage-4.5.alpha0/spkg/build/pynac-0.2.0.p4/src'
make[1]: Leaving directory
`/export/home/drkirkby/sage-4.5.alpha0/spkg/build/pynac-0.2.0.p4/src'
Now cleaning up tmp files.
rm: Cannot remove any directory in the path of the current working directory
/export/home/drkirkby/sage-4.5.alpha0/spkg/build/pynac-0.2.0.p4
Making Sage/Python scripts relocatable...
Making script relocatable
Finished installing pynac-0.2.0.p4.spkg
Not very convincing is it?
PS, as reported at
http://trac.sagemath.org/sage_trac/ticket/7861
pynac was not building 64-bit on OpenSolaris. I've managed to find a workaround
(aka hack) for this. I think the package needs a bit of work to be honest, as
its use of libtool is just not working right. But I've managed to get it to
build by forcing it to look in for the gcc libraries in the place where the
64-bit ones are. libtool should handle all this automatically, but something is
wrong with how pynac is using libtool I think.
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
