Re: [sage-devel] Use NTL upstream build system in Sage's spkg

On Tuesday, August 7, 2012 11:42:41 AM UTC+2, Jean-Pierre Flori wrote: > > Updated spkg uploaded at #11635, link is > http://perso.telecom-paristech.fr/~flori/sage/ntl-5.5.2.p0.spkg > > If someone could check if it's as functional as the previous one on Mac > OSX and Solaris, and exotic Linuxes,

Re: [sage-devel] Use NTL upstream build system in Sage's spkg

Updated spkg uploaded at #11635, link is http://perso.telecom-paristech.fr/~flori/sage/ntl-5.5.2.p0.spkg If someone could check if it's as functional as the previous one on Mac OSX and Solaris, and exotic Linuxes, without libtool installed (or with it, it explicitely points NTL to the generated

Re: [sage-devel] Use NTL upstream build system in Sage's spkg

> You could simply copy them from the system (in my installation, this is > /usr/share/libtool/config) > I guess that's what the aclocal/autoconf comination did in the end, but now if it does not work, it will be easier to blame autotools :) -- -- To post to this group, send an email to sa

Re: [sage-devel] Use NTL upstream build system in Sage's spkg

On 2012-08-07 10:09, Jean-Pierre Flori wrote: > > > On Tuesday, August 7, 2012 8:47:46 AM UTC+2, Jeroen Demeyer wrote: > > On 2012-08-06 20:32, Julien Puydt wrote: > > Ouch. Then indeed, they have one more build-time dep than necessary. > I guess the correct thing to do for Sage woul

Re: [sage-devel] Use NTL upstream build system in Sage's spkg

It seems I've got something looking good. I'll post an updated spkg in #11635 soon. -- -- 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://gro

Re: [sage-devel] Use NTL upstream build system in Sage's spkg

Adding AC_INIT and AC_OUTPUT seems to please aclocal -- -- 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

Re: [sage-devel] Use NTL upstream build system in Sage's spkg

On Tuesday, August 7, 2012 8:47:46 AM UTC+2, Jeroen Demeyer wrote: > > On 2012-08-06 20:32, Julien Puydt wrote: > > Ouch. Then indeed, they have one more build-time dep than necessary. > I guess the correct thing to do for Sage would be to ship libtool inside > the spkg (this is what is usuall

Re: [sage-devel] Use NTL upstream build system in Sage's spkg

On 2012-08-06 20:32, Julien Puydt wrote: > Ouch. Then indeed, they have one more build-time dep than necessary. I guess the correct thing to do for Sage would be to ship libtool inside the spkg (this is what is usually done for autotools projects anyway). -- -- To post to this group, send an ema

Re: [sage-devel] Use NTL upstream build system in Sage's spkg

On 2012-08-06 19:19, Jean-Pierre Flori wrote: > The problem here is that NTL does not use autotools, but only libtool. > In particular its configure script does not generate a suitable libtool, > but it expects you to provide one (which should be functional on your > system). I consider that an ups

Re: [sage-devel] Use NTL upstream build system in Sage's spkg

Le lundi 6 août 2012 20:32:22 UTC+2, Snark a écrit : > > Le 06/08/2012 19:19, Jean-Pierre Flori a �crit : > > As far as I understand this : > > http://www.gnu.org/software/libtool/manual/libtool.html#Configuring > >

Re: [sage-devel] Use NTL upstream build system in Sage's spkg

Le 06/08/2012 19:19, Jean-Pierre Flori a écrit : As far as I understand this : http://www.gnu.org/software/libtool/manual/libtool.html#Configuring the correct libtool script is created by the configure script,

Re: [sage-devel] Use NTL upstream build system in Sage's spkg

> As far as I understand this : > http://www.gnu.org/software/libtool/manual/libtool.html#Configuring > > the correct libtool script is created by the configure script, tailored > for your system&compiler -- nothing from the system is used. > > Are you that sure there is a problem here? > >

Re: [sage-devel] Use NTL upstream build system in Sage's spkg

Le 06/08/2012 19:09, Jean-Pierre Flori a écrit : If I understood correctly, when you use autotools, then configure more or less generates a suitable libtool (using config.guess/ltmain.sh/aclocal.m4 and another file I forgot, which in turn are generate by autoconf/aclocal/libtoolize tools) for you

Re: [sage-devel] Use NTL upstream build system in Sage's spkg

> Oh, isn't libtool like the rest of autotools : only necessary for people > developing upstream, but not for those who just want to compile the > project? > > Snark on #sagemath > If I understood correctly, when you use autotools, then configure more or less generates a suitable libtool (us

Re: [sage-devel] Use NTL upstream build system in Sage's spkg

Le 06/08/2012 18:34, Jean-Pierre Flori a écrit : But the use of libtool is problematic because this is not a dependency for Sage. Oh, isn't libtool like the rest of autotools : only necessary for people developing upstream, but not for those who just want to compile the project? Snark on #sa

[sage-devel] Use NTL upstream build system in Sage's spkg

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 curre