[sage-devel] Re: Sagecell v1 and matlab as default interpreter

2012-08-07 Thread Jason Grout
On 8/7/12 9:33 PM, fero wrote: Dear all, I open a new post in order to be more specific. Is there any way to open a Sagecell that use matlab as default interpreter (or have a "select" box, like I can do in the notebook) ? It isn't built in to the sage cell right now. I wonder if you automat

[sage-devel] Sagecell v1 and matlab as default interpreter

2012-08-07 Thread fero
Dear all, I open a new post in order to be more specific. Is there any way to open a Sagecell that use matlab as default interpreter (or have a "select" box, like I can do in the notebook) ? Anyone can help me in reaching this result please? I'd like to abandon the notebook interface, because I

Re: [sage-devel] spkg size and regenerating configure scripts

2012-08-07 Thread Volker Braun
We are shipping > 300mb of compressed sources, I don't think we should be concerned with the size of autotool-generated scripts. In fact, I would argue its better to use newer autotools than some ancient version just because you want to save some disk space. What would be nice is some conventio

Re: [sage-devel] CTRL-C crashes the notebook in 5.2

2012-08-07 Thread Daniel Smertnig
Hi, I posted about this to a thread on sage-release about the same problem, but realised that sage-devel might be the better place for this. Short answer: PyOpenSSL 0.12 that comes with sagenb seems to be the culprit (indirectly, because it fails to load and messes up dlopen). Installing 0.13

Re: [sage-devel] spkg size and regenerating configure scripts

2012-08-07 Thread Jean-Pierre Flori
On Tuesday, August 7, 2012 8:01:16 PM UTC+2, Jeroen Demeyer wrote: > > On 2012-08-07 19:10, Jean-Pierre Flori wrote: > > Dear all, > > > > While working on #9167 and #13325, I was faced with the necessity of > > modifying upstream build systems based on autotools. > > I thought the right way

Re: [sage-devel] spkg size and regenerating configure scripts

2012-08-07 Thread Jeroen Demeyer
On 2012-08-07 19:10, Jean-Pierre Flori wrote: > Dear all, > > While working on #9167 and #13325, I was faced with the necessity of > modifying upstream build systems based on autotools. > I thought the right way to do so was to modify the autotools files and > regenerate the build system with the

Re: [sage-devel] spkg size and regenerating configure scripts

2012-08-07 Thread Jean-Pierre Flori
> Why would hg follow upstream? Shouldn't it only follow the changes to > the supporting files? > > Snark on #sagemath > Indeed, hg does not follow upstream, but in order to keep a vanilla src directory, I produce patches, put them in SPKG_ROOT/patches and there they got tracked. -- -- T

Re: [sage-devel] spkg size and regenerating configure scripts

2012-08-07 Thread Julien Puydt
Le 07/08/2012 19:10, Jean-Pierre Flori a écrit : Dear all, While working on #9167 and #13325, I was faced with the necessity of modifying upstream build systems based on autotools. I thought the right way to do so was to modify the autotools files and regenerate the build system with the autotoo

[sage-devel] spkg size and regenerating configure scripts

2012-08-07 Thread Jean-Pierre Flori
Dear all, While working on #9167 and #13325, I was faced with the necessity of modifying upstream build systems based on autotools. I thought the right way to do so was to modify the autotools files and regenerate the build system with the autotools machinery. This has the unfortunate consequenc

Re: [sage-devel] Sage Build from source not working for 5.1 nor 5.2

2012-08-07 Thread Gregg
Hi William, I would worry about losing compatibility with other systems if I updgrade my OS too much, but when I am done traveling, an upgrade to Mac OS 10.5 should be possible. However, talking to several others last week, at FPSAC it appears that this is not a problem unique to me though, ma

[sage-devel] Re: Sage Build from source not working for 5.1 nor 5.2

2012-08-07 Thread Gregg
Here is the relevant file. On Friday, August 3, 2012 6:49:13 PM UTC-5, Volker Braun wrote: > > The problem is > > > /usr/bin/ld: warning can't open dynamic library: > /Applications/sage-5.2/spkg/build/pari-2.5.1.p3/src/Odarwin-i386/libpari-gmp.dylib > > referenced from: /Applications/sage-5.2/

[sage-devel] sage foundation in austria

2012-08-07 Thread Harald Schilly
Hello Sage Developers & Friends! Last week I started to work on creating a "Sage Foundation". There were some issues in the recent past and this is also something which is sitting in the back of my head for some time now. I'm certain Sage will benefit from that and will get on the next level, if t

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

2012-08-07 Thread Volker Braun
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 th

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

2012-08-07 Thread Jean-Pierre Flori
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

2012-08-07 Thread Jean-Pierre Flori
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

2012-08-07 Thread Jean-Pierre Flori
> 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

2012-08-07 Thread Jeroen Demeyer
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

2012-08-07 Thread Jean-Pierre Flori
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

2012-08-07 Thread Jean-Pierre Flori
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

2012-08-07 Thread Jean-Pierre Flori
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

[sage-devel] Re: error building from source (sagenb-0.9.1)

2012-08-07 Thread Keshav Kini
Luis Finotti writes: > (Shouldn't this be in the README.txt?) There's a lot wrong with the README.txt... This requirement for the OpenSSL dev headers is mentioned in the installation documentation, though - http://www.sagemath.org/doc/installation/source.html -Keshav Join us in #sagemath o