In the new atlas-3.10.0 spkg (http://trac.sagemath.org/10508) I faced the same problem, I needed libtool to build a shared library but atlas doesn't use autoconf and doesn't install libtool. It is possible to install libtool globally, but it is recommended that it is generated by autotools on the fly.
In the atlas spkg I solved this by adding a stub autotools project that creates libtool and then builds the shared libraries from the static libraries. On Monday, August 6, 2012 12:34:48 PM UTC-4, Jean-Pierre Flori wrote: > > Dear all, > > In order to properly solve #11635 for NTL on Cygwin, and in order to > sumplify the NTL spkg, we could use NTL own build system, rather than the > one which was crafted before NTL had a portable one. > I've got no problems build static and shared libraries on Linux and Cygwin > with the current one which uses (by default the system wide) libtool for > compiling, linking and installing. > But the use of libtool is problematic because this is not a dependency for > Sage. > Another solution would be to include the four files needed to generate > libtool in the NTL spkg (most spkg for projects using autotools do that > already) and generate it from spkg-intall before running configure. > The problem is I have no clue where I should get such files, or how to > generate them using libtoolize, aclocal or I don't know what, or if it's > even possible to do that for a non-autotool projects. > > Best, > JP > > -- -- 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
