[sage-devel] Re: Issues with meataxe on 32bit systems (Cannot select field GF(9) in file matcore.c)

[Dima Pasechnik]

Hi Thierry,

do you realise that Pentium III has been out of production for 15 years?
It does not strike me as an important issue that an emulator for this truly 
museum piece of hardware does not produce
binaries compatible with other, slightly less outdated, pieces of 
hardware...

I understand that most probably you'd like to build a binary that works on 
as many archs as possible.
I am not sure that the approach to use such an outdated piece is the right 
one; nothing gets seriously tested 
on such hardware nowadays. (E.g. I doubt that gcc is tested on Pentium III 
nowadays...).

On Friday, September 23, 2016 at 6:38:55 AM UTC, Simon King wrote:
>
> Hi Thierry, 
>
> On 2016-09-22, Thierry > wrote: 
> > Yes, though in the first case the (pentium3 emulated) processor is only 
> > capable of 32 bit (no lm flag), while in the other cases (genuine 
> pentium4 
> > and genuine core2duo), while the kernel is 32bit, the proc is capable of 
> > 64bit. 
>
> Not sure if that can be a problem. 
>
> >> Does meataxe work, if you do *not* move the binary to a different 
> >> platform but keep it on the platform it was compiled with? 
> > 
> > Yes. 
>
> "Yes" for both of the two platforms? 
>
> Best regards, 
> Simon 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Make some fun

[Dima Pasechnik]

On Thursday, September 22, 2016 at 1:14:08 PM UTC, Luca De Feo wrote:
>
> I just tried `make -B` inside a source install. I recommend it :) 
>
> make -B makes all targets (including distclean etc)
For even more fun, try "sudo rm -f /" next time ;-)
 

> Luca 
>
> P.S.: Seriously, I am not a Makefile expert, I don't know what's 
> happening here, but infinite recursion feels bad. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Getting rid of reset() and restore()?

[Dima Pasechnik]

On Monday, September 19, 2016 at 4:56:02 PM UTC, Jeroen Demeyer wrote:
>
> On 2016-09-19 18:50, William Stein wrote: 
> > That's only "dangerous" if you expect reset to do the same thing as 
> > restart sage 
>
> I would guess that users *do* expect that. 
>

various CASs have similar facilities, e.g. Maple has "restart" which is not 
a complete restart from scratch.
Thus users won't always expect reset to be as disruptive is a complete 
restart from scratch.
 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage and pylint

[Dima Pasechnik]

On Thursday, September 22, 2016 at 3:38:10 PM UTC, Salvatore Stella wrote:
>
> Hi Erik, 
> no options. As an example of the errors I get let's consider the ticket I 
> am 
> working on (#21254). 
>
> I installed pylint via 
>
> $ sage -pip install pylint 
>
> my sage install is in /opt/sage so 
>
> $ /opt/sage/local/bin/pylint 
> /opt/sage/src/sage/algebras/cluster_algebra.py | grep E: | head 
>

IMHO you should run pylint in sage shell, i.e. first do "sage -sh" and only 
at its prompt start pylint.
The way you try doesn't set the environment right.

HTH,
Dima
 

> No config file found, using default configuration 
> E:327, 0: No name 'morphism' in module 'sage.categories' 
> (no-name-in-module) 
> E:335, 0: No name 'constructor' in module 'sage.matrix' 
> (no-name-in-module) 
> E:337, 0: No name 'cachefunc' in module 'sage.misc' 
> (no-name-in-module) 
> E:338, 0: No name 'misc_c' in module 'sage.misc' 
> (no-name-in-module) 
> E:339, 0: No name 'free_module_element' in module 'sage.modules' 
> (no-name-in-module) 
> E:341, 0: No name 'integer' in module 'sage.rings' 
> (no-name-in-module) 
> E:342, 0: No name 'integer_ring' in module 'sage.rings' 
> (no-name-in-module) 
> E:347, 0: No name 'element_wrapper' in module 'sage.structure' 
> (no-name-in-module) 
> E:348, 0: No name 'parent' in module 'sage.structure' 
> (no-name-in-module) 
> E:349, 0: No name 'sage_object' in module 'sage.structure' 
> (no-name-in-module) 
>
> I get many more warnings about lines being too long, having too many/too 
> few 
> methods etc but I do not care about those. 
>
> Something weird: line 326 and 327 are 
> from sage.categories.homset import Hom 
> from sage.categories.morphism import SetMorphism   
> 
> pylint complains only about the second. 
>
> Best 
> S. 
>
>
>
>
> * Erik Bray > [2016-09-22 17:24:05]: 
>
> >On Fri, Sep 16, 2016 at 1:12 PM, VulK > 
> wrote: 
> >> Hi, 
> >> I thought this was a question for sage-devel because it is about 
> tickets I 
> >> am currently working on (#21254 specifically). Sorry for the wrong 
> >> assumption. 
> >> 
> >> I did try sage -pip install pylint before posting but the results were 
> >> identical (even launching it from within sage -sh) 
> > 
> >That sounds suspicious, though I admit I haven't tried it myself yet. 
> >With what options did you run pylint?  If it installed correctly into 
> >Sage's Python it should work. 
> > 
> >I wouldn't mind getting that working myself.  It would be very nice to 
> >see what cleanup pylint can suggest (though a foolish consistency is 
> >the hobgoblin of little minds--I suspect pylint will require a lot of 
> >exceptions for sage :) 
> > 
> >> * Thierry > [2016-09-16 
> 13:08:10]: 
> >> 
> >> 
> >>> Hi, 
> >>> 
> >>> note that https://ask.sagemath.org is a nice place to ask such 
> questions 
> >>> that are not related to sage development but still interesting. 
> >>> 
> >>> Anyway, Sage uses its own Python install, so you should install pylint 
> >>> within Sage and import it from there. 
> >>> 
> >>> A priori, the following should work: 
> >>> 
> >>> sage -pip install pylint 
> >>> 
> >>> If you really want to use the pylint from your distro, you should add 
> the 
> >>> path to your distro's '/${WHATEVER}/python2.7/dist-packages' directory 
> to 
> >>> Sage's PYTHONPATH, at your own risks. 
> >>> 
> >>> Ciao, 
> >>> Thierry 
> >>> 
> >>> 
> >>> 
> >>> On Fri, Sep 16, 2016 at 12:55:29PM +0200, VulK wrote: 
>  
>  Dear all, 
>  I am trying to use pylint to validate some of the code in a patch I 
> wrote 
>  for sage and, unsurprisingly, I am getting several complaints because 
> my 
>  system-wide pylint can't resolve modules like sage.something. 
>  
>  What is the correct way of doing this? Is there any other alternative 
> to 
>  pylint that I should use instead? 
>  Thanks 
>  S. 
>  
>  
>  -- 
>  You received this message because you are subscribed to the Google 
> Groups 
>  "sage-devel" group. 
>  To unsubscribe from this group and stop receiving emails from it, 
> send an 
>  email to sage-devel+...@googlegroups.com . 
>  To post to this group, send email to sage-...@googlegroups.com 
> . 
>  Visit this group at https://groups.google.com/group/sage-devel. 
>  For more options, visit https://groups.google.com/d/optout. 
> >>> 
> >>> 
> >>> -- 
> >>> You received this message because you are subscribed to the Google 
> Groups 
> >>> "sage-devel" group. 
> >>> To unsubscribe from this group and stop receiving emails from it, send 
> an 
> >>> email to sage-devel+...@googlegroups.com . 
> >>> To post to this group, send email to sage-...@googlegroups.com 
> . 
> >>> Visit this group at https://groups.google.com/group/sage-devel. 
> >>> For more options, visit https://groups.google.com/d/optout. 
> >> 
> >

Re: [sage-devel] Re: Make some fun

[Luca De Feo]

> make -B makes all targets (including distclean etc)
> For even more fun, try "sudo rm -f /" next time ;-)

I don't think that's what was happening on my side. Here's what I
have, make repeatedly tries to build build/make/Makefile :

$ ./sage --version
SageMath version 7.4.beta5, Release Date: 2016-09-16
$ make -B build
make build/make/Makefile
make[1]: Entering directory '/home/defeo/sage'
make build/make/Makefile
make[2]: Entering directory '/home/defeo/sage'
make build/make/Makefile
make[3]: Entering directory '/home/defeo/sage'
make build/make/Makefile
make[4]: Entering directory '/home/defeo/sage'
make build/make/Makefile
make[5]: Entering directory '/home/defeo/sage'
make build/make/Makefile
make[6]: Entering directory '/home/defeo/sage'
make build/make/Makefile
make[7]: Entering directory '/home/defeo/sage'
make build/make/Makefile
make[8]: Entering directory '/home/defeo/sage'
make build/make/Makefile

and it goes on... it quickly reaches thousands of nested invocations,
only solution is to kill it.

On another machine this fails after exactly 234 invocations. My guess
is that this is dependent on the version of make.

Luca

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] sage4 patchbot

[Jeroen Demeyer]

On 2016-09-23 08:51, Ralf Stephan wrote:

What has that to do with stopping the bot (or monitoring it at all, for
that matter)?


Nothing with that. But it has *everything* to do with fixing the bot.

--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Sage's references: new policy?

[Dima Pasechnik]

On Thursday, September 22, 2016 at 4:32:11 AM UTC, Nils Bruin wrote:
>
> On Tuesday, September 20, 2016 at 4:03:27 PM UTC-7, John H Palmieri wrote:
>>
>> As discussed in another thread [1]_ on sage-devel recently, I propose 
>> changing our policy toward references:
>>
>> - all references should be put into a master bibliography file
>>
>
> There is one significant drawback to this: it will mean that a lot of 
> ticket branches will be modifying this file, so merge conflicts between 
> tickets may become more prevalent. If we can do something to ensure that 
> resolving these merge conflicts is likely to fall within what standard 
> merge strategies can do automatically we should probably do that.
>

I agree - however, perhaps it's better to think of using several bibtex 
files (which is perfectly possible in LaTeX); e.g. one for number theory, 
one for group theory, one for the commutative algebra, etc.

 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error building sage 7.3 on Fedora 24 x86_64

[Lennart Jern]

Okay, that makes sense. I had missed gcc-gfortran, thought it was enough to 
have just gcc!

Thank you for the help!

On Thursday, September 22, 2016 at 9:06:46 PM UTC+2, Volker Braun wrote:
>
> The easiest solution would be to install the dependencies so that Sage 
> doesn't attempt to compile its own toolchain:
>
>
> http://doc.sagemath.org/html/en/installation/source.html#linux-prerequisite-installation
>
>
>
> On Thursday, September 22, 2016 at 8:45:34 PM UTC+2, Lennart Jern wrote:
>>
>> Hello,
>>
>> I'm attempting to build sage on Fedora 24 as a first step toward 
>> contributing to the project. The build fails at gcc however, and I'm 
>> uncertain about how to proceed. I attached the relevant log.
>> Any advice appreciated!
>>
>> Lennart
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Make some fun

[Dima Pasechnik]

I mean to say that I don't see how "make -B" can work on anything but very 
trivial makefiles

On Friday, September 23, 2016 at 9:11:50 AM UTC, Luca De Feo wrote:
>
> > make -B makes all targets (including distclean etc) 
> > For even more fun, try "sudo rm -f /" next time ;-) 
>
> I don't think that's what was happening on my side. Here's what I 
> have, make repeatedly tries to build build/make/Makefile : 
>
> $ ./sage --version 
> SageMath version 7.4.beta5, Release Date: 2016-09-16 
> $ make -B build 
> make build/make/Makefile 
> make[1]: Entering directory '/home/defeo/sage' 
> make build/make/Makefile 
> make[2]: Entering directory '/home/defeo/sage' 
> make build/make/Makefile 
> make[3]: Entering directory '/home/defeo/sage' 
> make build/make/Makefile 
> make[4]: Entering directory '/home/defeo/sage' 
> make build/make/Makefile 
> make[5]: Entering directory '/home/defeo/sage' 
> make build/make/Makefile 
> make[6]: Entering directory '/home/defeo/sage' 
> make build/make/Makefile 
> make[7]: Entering directory '/home/defeo/sage' 
> make build/make/Makefile 
> make[8]: Entering directory '/home/defeo/sage' 
> make build/make/Makefile 
>
> and it goes on... it quickly reaches thousands of nested invocations, 
> only solution is to kill it. 
>
> On another machine this fails after exactly 234 invocations. My guess 
> is that this is dependent on the version of make. 
>
> Luca 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] crash after compiling sagemanifolds sage 7.3 (ppa aims)

[aishen]

New ubuntu 16.04 fresh install. I got it already on last week on an old 
xenial.
What do I do ? Forgetting about sagemanifolds ?
Or get the sagemath binary which works ?
I would like to keep the deb because it updating automatically
Thanks for your help
Best
Henri
real41m33.940s
user40m36.776s
sys1m0.760s

Installation of SageManifolds 0.9.1 completed!

pi@pc:/usr/lib/sagemath$ sage
┌┐
│ SageMath version 7.3, Release Date: 2016-08-04 │
│ Type "notebook()" for the browser-based notebook interface.│
│ Type "help()" for help.│
└┘

**

Oops, Sage crashed. We do our best to make it stable, but...

A crash report was automatically generated with the following information:
  - A verbatim copy of the crash traceback.
  - A copy of your input history during this session.
  - Data on your current Sage configuration.

It was left in the file named:
'/home/pi/.sage/ipython_genutils-0.1.0/Sage_crash_report.txt'
If you can email this file to the developers, the information in it will 
help
them in understanding and correcting the problem.

You can mail it to: sage-support at sage-supp...@googlegroups.com
with the subject 'Sage Crash Report'.

If you want to do it now, the following command will work (under Unix):
mail -s 'Sage Crash Report' sage-supp...@googlegroups.com < 
/home/pi/.sage/ipython_genutils-0.1.0/Sage_crash_report.txt

To ensure accurate tracking of this issue, please file a report about it at:
http://trac.sagemath.org

Hit  to quit (your terminal may close):
pi@pc:/usr/lib/sagemath$ 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Sage's references: new policy?

[Johan S . H . Rosenkilde]

>>> As discussed in another thread [1]_ on sage-devel recently, I propose 
>>> changing our policy toward references:
>>>
>>> - all references should be put into a master bibliography file
>>>
>>
>> There is one significant drawback to this: it will mean that a lot of 
>> ticket branches will be modifying this file, so merge conflicts between 
>> tickets may become more prevalent. If we can do something to ensure that 
>> resolving these merge conflicts is likely to fall within what standard 
>> merge strategies can do automatically we should probably do that.

Will it really be that bad? The proposed master bibliography is sorted
alphabetically by first author, so conflicts should only occur when two
tickets insert/modify citations right next to each other (or with
perhaps 1 citation between them). With >1000 references right now,
that's not going to cause too many extra conflicts, I think:

If there's 1000 "equidistant" references and a single release has
tickets that create 10 new random references (this is high, I think),
then there's roughly 20% chance that 1 pair of these references will be
within 1 of each other in the existing reference list.

Dima Pasechnik writes:
> I agree - however, perhaps it's better to think of using several bibtex 
> files (which is perfectly possible in LaTeX); e.g. one for number theory, 
> one for group theory, one for the commutative algebra, etc.

Hmm, that seems complicated: Wouldn't many references naturally fall
into multiple such categories, so every time you want to add a reference
you would have to grep for it across all files.

Best,
Johan

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] pre-built buildbot docker images?

[Erik Bray]

On Thu, Sep 22, 2016 at 10:50 PM, William Stein  wrote:
> Hi,
>
> Is there a Sage buildbot docker image, e.g, something so "any idiot" can
> just go
>
>docker run blah blah sagemath-buildbot-ubuntu
>
> or
>
>docker run blah blah sagemath-buildbot-centos
>
> and have a build bot running... and when they want to clean up, just delete
> the docker container?

Not yet that I know of.  One thing I've had in mind to do for some
time is cobble together a template Dockerfile from the ones I already
have, so that it will be easier to build sage docker containers on top
of different base images (see
https://github.com/sagemath/docker-images/issues/12)

On top of these one could add build-bot images that have the base sage
images plus buildbot configured.  This is definitely what we should do
for future build infrastructure...

Right now I'm more focused on getting a Windows buildbot going (which
will be impossible until and unless I fix the Cygwin build, which I
had 100% working until I merged in
https://trac.sagemath.org/ticket/17635 :)

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: crash after compiling sagemanifolds sage 7.3 (ppa aims)

[Eric Gourgoulhon]

Hi, 

Le vendredi 23 septembre 2016 11:40:01 UTC+2, aishen a écrit :
>
>
> It was left in the file named:
> '/home/pi/.sage/ipython_genutils-0.1.0/Sage_crash_report.txt'
> If you can email this file to the developers, the information in it will 
> help
> them in understanding and correcting the problem.
>
>
Could you please send the above Sage_crash_report.txt file?
Besides, can you tell which version of SageMath you are using? Is it the 
one from the Ubuntu PPA package? 
Thanks. 
Eric. 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage and pylint

[Erik Bray]

On Thu, Sep 22, 2016 at 5:38 PM, VulK  wrote:
> Hi Erik,
> no options. As an example of the errors I get let's consider the ticket I am
> working on (#21254).
>
> I installed pylint via
>
> $ sage -pip install pylint
> my sage install is in /opt/sage so
>
> $ /opt/sage/local/bin/pylint
> /opt/sage/src/sage/algebras/cluster_algebra.py | grep E: | head
> No config file found, using default configuration
> E:327, 0: No name 'morphism' in module 'sage.categories'
> (no-name-in-module)
> E:335, 0: No name 'constructor' in module 'sage.matrix'
> (no-name-in-module)
> E:337, 0: No name 'cachefunc' in module 'sage.misc'
> (no-name-in-module)
> E:338, 0: No name 'misc_c' in module 'sage.misc' (no-name-in-module)
> E:339, 0: No name 'free_module_element' in module 'sage.modules'
> (no-name-in-module)
> E:341, 0: No name 'integer' in module 'sage.rings'
> (no-name-in-module)
> E:342, 0: No name 'integer_ring' in module 'sage.rings'
> (no-name-in-module)
> E:347, 0: No name 'element_wrapper' in module 'sage.structure'
> (no-name-in-module)
> E:348, 0: No name 'parent' in module 'sage.structure'
> (no-name-in-module)
> E:349, 0: No name 'sage_object' in module 'sage.structure'
> (no-name-in-module)

I don't think pylint supports Cython modules, so that would probably do it.


> * Erik Bray  [2016-09-22 17:24:05]:
>
>
>> On Fri, Sep 16, 2016 at 1:12 PM, VulK  wrote:
>>>
>>> Hi,
>>> I thought this was a question for sage-devel because it is about tickets
>>> I
>>> am currently working on (#21254 specifically). Sorry for the wrong
>>> assumption.
>>>
>>> I did try sage -pip install pylint before posting but the results were
>>> identical (even launching it from within sage -sh)
>>
>>
>> That sounds suspicious, though I admit I haven't tried it myself yet.
>> With what options did you run pylint?  If it installed correctly into
>> Sage's Python it should work.
>>
>> I wouldn't mind getting that working myself.  It would be very nice to
>> see what cleanup pylint can suggest (though a foolish consistency is
>> the hobgoblin of little minds--I suspect pylint will require a lot of
>> exceptions for sage :)
>>
>>> * Thierry  [2016-09-16 13:08:10]:
>>>
>>>
 Hi,

 note that https://ask.sagemath.org is a nice place to ask such questions
 that are not related to sage development but still interesting.

 Anyway, Sage uses its own Python install, so you should install pylint
 within Sage and import it from there.

 A priori, the following should work:

 sage -pip install pylint

 If you really want to use the pylint from your distro, you should add
 the
 path to your distro's '/${WHATEVER}/python2.7/dist-packages' directory
 to
 Sage's PYTHONPATH, at your own risks.

 Ciao,
 Thierry



 On Fri, Sep 16, 2016 at 12:55:29PM +0200, VulK wrote:
>
>
> Dear all,
> I am trying to use pylint to validate some of the code in a patch I
> wrote
> for sage and, unsurprisingly, I am getting several complaints because
> my
> system-wide pylint can't resolve modules like sage.something.
>
> What is the correct way of doing this? Is there any other alternative
> to
> pylint that I should use instead?
> Thanks
> S.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.



 --
 You received this message because you are subscribed to the Google
 Groups
 "sage-devel" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an
 email to sage-devel+unsubscr...@googlegroups.com.
 To post to this group, send email to sage-devel@googlegroups.com.
 Visit this group at https://groups.google.com/group/sage-devel.
 For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "sage-devel" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to sage-devel+unsubscr...@googlegroups.com.
>>> To post to this group, send email to sage-devel@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/sage-devel.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> em

[sage-devel] Re: crash after compiling sagemanifolds sage 7.3 (ppa aims)

[Eric Gourgoulhon]

OK I could reproduce the error, with the following set-up:

- Ubuntu 16.04 x86_64
- SageMath 7.3 from AIMS PPA installed as follows:
sudo -E apt-add-repository -y ppa:aims/sagemath
sudo -E apt-get update
sudo -E apt-get install sagemath-upstream-binary-full
- SageManifold 0.9.1 installed as follows
cd /usr/lib/sagemath
sudo wget -N http://sagemanifolds.obspm.fr/spkg/sm-install.sh
sudo bash sm-install.sh

The error is (cf. the attached crash report file)

ImportError: 
/usr/lib/sagemath/local/lib/python2.7/site-packages/sage/symbolic/pynac.so: 
undefined symbol: 
_ZN5GiNaC8constantC1ENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPFNS_2exEjP7_objectERKS6_j

Actually, this error does not seem to be connected to SageManifolds (which 
does not touch pynac.pyx) but to the inability of this version of SageMath 
to rebuild itself: it has already been reported in a context different from 
SageManifolds: 
cf. https://groups.google.com/d/msg/sage-support/Qg5rpO43daE/zDH_Y3gvCQAJ
There, it was suggested this might be due to the pretty old version of gcc 
(4.8.4) used to buid the binary. Do the AIMS PPA maintainers have an 
opinion on that ?

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
***

IPython post-mortem report

{'commit_hash': u'b630b41',
 'commit_source': 'installation',
 'default_encoding': 'UTF-8',
 'ipython_path': '/usr/lib/sagemath/local/lib/python2.7/site-packages/IPython',
 'ipython_version': '4.2.1',
 'os_name': 'posix',
 'platform': 'Linux-4.4.0-38-generic-x86_64-with-debian-stretch-sid',
 'sys_executable': '/usr/lib/sagemath/local/bin/python',
 'sys_platform': 'linux2',
 'sys_version': '2.7.10 (default, Aug  6 2016, 15:34:26) \n[GCC 4.8.4]'}

***



***

Crash traceback:

---
---
ImportError   Python 2.7.10: /usr/lib/sagemath/local/bin/python
   Fri Sep 23 14:13:24 2016
A problem occurred executing Python code.  Here is the sequence of function
calls leading up to the error, with the most recent (innermost) call last.
/usr/lib/sagemath/src/bin/sage-ipython in ()
  1 #!/usr/bin/env python
  2 # -*- coding: utf-8 -*-
  3 """
  4 Sage IPython startup script.
  5 """
  6 
  7 # Install extra readline commands before IPython initialization
  8 from sage.repl.readline_extra_commands import *
  9 
 10 from sage.repl.interpreter import SageTerminalApp
 11 
 12 app = SageTerminalApp.instance()
---> 13 app.initialize()
global app.initialize = >
 14 app.start()

 in initialize(self=, argv=None)

/usr/lib/sagemath/local/lib/python2.7/site-packages/traitlets/config/application.pyc
 in catch_config_error(method=, 
app=, *args=(None,), **kwargs={})
 59 
 60 
#-
 61 # Application class
 62 
#-
 63 
 64 @decorator
 65 def catch_config_error(method, app, *args, **kwargs):
 66 """Method decorator for catching invalid config 
(Trait/ArgumentErrors) during init.
 67 
 68 On a TraitError (generally caused by bad config), this will print 
the trait's
 69 message, and exit the app.
 70 
 71 For use on init methods, to prevent invoking excepthook on invalid 
input.
 72 """
 73 try:
---> 74 return method(app, *args, **kwargs)
method = 
app = 
args = (None,)
kwargs = {}
 75 except (TraitError, ArgumentError) as e:
 76 app.print_help()
 77 app.log.fatal("Bad config encountered during initialization:")
 78 app.log.fatal(str(e))
 79 app.log.debug("Config at the time: %s", app.config)
 80 app.exit(1)
 81 
 82 
 83 class ApplicationError(Exception):
 84 pass
 85 
 86 
 87 class LevelFormatter(logging.Formatter):
 88 """Formatter with additional `highlevel` record
 89 

/usr/lib/sagemath/local/lib/python2.7/site-packages/IPython/terminal/ipapp.pyc 
in initialize(self=, argv=None)
290 
291 return super(TerminalIPythonApp, self).parse_command_line(argv)
292 
   

[sage-devel] Re: crash after compiling sagemanifolds sage 7.3 (ppa aims)

[Eric Gourgoulhon]

PS (to aishen): while this problem is fixed, you may consider installing in 
your home directory SageMath 7.3 from the file 
sage-7.3-Ubuntu_16.04-x86_64.tar.bz2 downloaded from 
http://www.sagemath.org/download-linux.html. 
Installing SageManifolds in such a version has been tested successfully. 


-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: crash after compiling sagemanifolds sage 7.3 (ppa aims)

[henri.gir...@gmail.com]

Thank you very much for your help. I already use the binary sage7.3, in 
between, and it works fine with sagemanifolds. Sorry for the 
disturbance, but I like very much sagemanifolds and not being able to 
use it is disturbing for me. But now everything is fine and if they find 
a workaround I will retry it latter.


Best regards

Henri (aishen)


Le 23/09/2016 à 15:14, Eric Gourgoulhon a écrit :
PS (to aishen): while this problem is fixed, you may consider 
installing in your home directory SageMath 7.3 from the file 
sage-7.3-Ubuntu_16.04-x86_64.tar.bz2 downloaded from 
http://www.sagemath.org/download-linux.html.

Installing SageManifolds in such a version has been tested successfully.


--
You received this message because you are subscribed to a topic in the 
Google Groups "sage-devel" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/sage-devel/z1XQDRt-OFs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
sage-devel+unsubscr...@googlegroups.com 
.
To post to this group, send email to sage-devel@googlegroups.com 
.

Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: crash after compiling sagemanifolds sage 7.3 (ppa aims)

[Jan Groenewald]

Hi

Thanks, Eric. The PPA for 16.04 is indeed the 14.04 binary in the PPA
copied forward. Let me look at what (time) it takes to upload the proper
16.04 binary.

In principle, I can continue to maintain and increase automation of this,
but time might become an issue. We have a customized Ubuntu called
aims-desktop that we redistribute, and first created the PPA for that. I
know it is used much more widely. For redistribution we contacted
Canonical's legal department after their IP policy was in the news, and
were told to redistribute modified copies we must 1) remove all Ubuntu
branding and rebuild *all*  So in future our incentive to spend time on
this might reduce.

Of course it is still not recommended to run sage -b as root and even less
so in the PPA. The PPA was always viewed as a temporary solution while
people are working on properly debianizing sage, a hard and multi-year
project, which will no doubt leave Debian/Ubuntu with a outdated sage.

Still we want to support knowledgable people doing this out of necessity
while sage-in-debian is not ready.

Regards,
Jan

On 23 September 2016 at 15:14, Eric Gourgoulhon 
wrote:

> PS (to aishen): while this problem is fixed, you may consider installing
> in your home directory SageMath 7.3 from the file
> sage-7.3-Ubuntu_16.04-x86_64.tar.bz2 downloaded from
> http://www.sagemath.org/download-linux.html.
> Installing SageManifolds in such a version has been tested successfully.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
  .~.
  /V\ Jan Groenewald
 /( )\www.aims.ac.za
 ^^-^^

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: crash after compiling sagemanifolds sage 7.3 (ppa aims)

[Jan Groenewald]

Hi

On 23 September 2016 at 15:46, Jan Groenewald  wrote:

> were told to redistribute modified copies we must 1) remove all Ubuntu
> branding and rebuild *all*
>


.. binaries, or 2) sign a license to redistribute to African universities
only (how gracious) and they would then not be able to redistribute freely.

(Sorry, accidentally cut some text).

Regards,
Jan

-- 
  .~.
  /V\ Jan Groenewald
 /( )\www.aims.ac.za
 ^^-^^

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: crash after compiling sagemanifolds sage 7.3 (ppa aims)

[Eric Gourgoulhon]

Hi Jan,

Thanks for your prompt and detailed answer, and for your efforts in 
offering this PPA to the community.

Best regards,

Eric.

Le vendredi 23 septembre 2016 15:49:07 UTC+2, Jan Groenewald a écrit :
>
> Hi
>
> On 23 September 2016 at 15:46, Jan Groenewald  > wrote:
>
>> were told to redistribute modified copies we must 1) remove all Ubuntu 
>> branding and rebuild *all* 
>>
>
>
> .. binaries, or 2) sign a license to redistribute to African universities 
> only (how gracious) and they would then not be able to redistribute freely.
>
> (Sorry, accidentally cut some text).
>
> Regards,
> Jan
>  
> -- 
>   .~. 
>   /V\ Jan Groenewald
>  /( )\www.aims.ac.za
>  ^^-^^ 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: crash after compiling sagemanifolds sage 7.3 (ppa aims)

[Jan Groenewald]

Hi

If everything debian-builds OK, there will be a package here in a few hours
in the dev PPA:
https://launchpad.net/~aims/+archive/ubuntu/sagemath-dev/+packages


Watch the build
https://launchpad.net/~aims/+archive/ubuntu/sagemath-dev/+build/10947743
which take s about an hour. If successful, publishing that in the PPA could
take anything
from 5 minute to 5 hours, depending on how busy launchpad is.

Please send me feedback before I copy to the stable PPA. I can't test that
this even opens the notebook now.

Regards,
Jan

On 23 September 2016 at 16:32, Eric Gourgoulhon 
wrote:

> Hi Jan,
>
> Thanks for your prompt and detailed answer, and for your efforts in
> offering this PPA to the community.
>
> Best regards,
>
> Eric.
>
> Le vendredi 23 septembre 2016 15:49:07 UTC+2, Jan Groenewald a écrit :
>>
>> Hi
>>
>> On 23 September 2016 at 15:46, Jan Groenewald  wrote:
>>
>>> were told to redistribute modified copies we must 1) remove all Ubuntu
>>> branding and rebuild *all*
>>>
>>
>>
>> .. binaries, or 2) sign a license to redistribute to African universities
>> only (how gracious) and they would then not be able to redistribute freely.
>>
>> (Sorry, accidentally cut some text).
>>
>> Regards,
>> Jan
>>
>> --
>>   .~.
>>   /V\ Jan Groenewald
>>  /( )\www.aims.ac.za
>>  ^^-^^
>>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
  .~.
  /V\ Jan Groenewald
 /( )\www.aims.ac.za
 ^^-^^

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: crash after compiling sagemanifolds sage 7.3 (ppa aims)

[henri.gir...@gmail.com]

I just had a look apparently it failed ?


Le 23/09/2016 à 17:11, Jan Groenewald a écrit :

Hi

If everything debian-builds OK, there will be a package here in a few 
hours in the dev PPA:
https://launchpad.net/~aims/+archive/ubuntu/sagemath-dev/+packages 



Watch the build 
https://launchpad.net/~aims/+archive/ubuntu/sagemath-dev/+build/10947743 

which take s about an hour. If successful, publishing that in the PPA 
could take anything

from 5 minute to 5 hours, depending on how busy launchpad is.

Please send me feedback before I copy to the stable PPA. I can't test 
that this even opens the notebook now.


Regards,
Jan

On 23 September 2016 at 16:32, Eric Gourgoulhon 
mailto:egourgoul...@gmail.com>> wrote:


Hi Jan,

Thanks for your prompt and detailed answer, and for your efforts
in offering this PPA to the community.

Best regards,

Eric.

Le vendredi 23 septembre 2016 15:49:07 UTC+2, Jan Groenewald a
écrit :

Hi

On 23 September 2016 at 15:46, Jan Groenewald
 wrote:

were told to redistribute modified copies we must 1)
remove all Ubuntu branding and rebuild *all*



.. binaries, or 2) sign a license to redistribute to African
universities only (how gracious) and they would then not be
able to redistribute freely.

(Sorry, accidentally cut some text).

Regards,
Jan
-- 
  .~.

  /V\ Jan Groenewald
 /( )\ www.aims.ac.za 
 ^^-^^

-- 
You received this message because you are subscribed to the Google

Groups "sage-devel" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to sage-devel+unsubscr...@googlegroups.com
.
To post to this group, send email to sage-devel@googlegroups.com
.
Visit this group at https://groups.google.com/group/sage-devel
.
For more options, visit https://groups.google.com/d/optout
.




--
  .~.
  /V\ Jan Groenewald
 /( )\ www.aims.ac.za 
 ^^-^^
--
You received this message because you are subscribed to a topic in the 
Google Groups "sage-devel" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/sage-devel/z1XQDRt-OFs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
sage-devel+unsubscr...@googlegroups.com 
.
To post to this group, send email to sage-devel@googlegroups.com 
.

Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: crash after compiling sagemanifolds sage 7.3 (ppa aims)

[Jan Groenewald]

Thanks, that was the second time. Third time also failed at 10 minutes
without buildlog.
launchpad does that sometimes but ususally 1 (or 2)  retries are enough.
4th retry is now showing a buildlog, and busy building, and is at 33
minutes, give it 30 more or so.

Regards,
Jan

On 23 September 2016 at 18:42, henri.gir...@gmail.com <
henri.gir...@gmail.com> wrote:

> I just had a look apparently it failed ?
>
> Le 23/09/2016 à 17:11, Jan Groenewald a écrit :
>
> Hi
>
> If everything debian-builds OK, there will be a package here in a few
> hours in the dev PPA:
> https://launchpad.net/~aims/+archive/ubuntu/sagemath-dev/+packages
> 
>
> Watch the build https://launchpad.net/~aims/+archive/ubuntu/sagemath-dev/+
> build/10947743
> 
> which take s about an hour. If successful, publishing that in the PPA
> could take anything
> from 5 minute to 5 hours, depending on how busy launchpad is.
>
> Please send me feedback before I copy to the stable PPA. I can't test that
> this even opens the notebook now.
>
> Regards,
> Jan
>
> On 23 September 2016 at 16:32, Eric Gourgoulhon 
> wrote:
>
>> Hi Jan,
>>
>> Thanks for your prompt and detailed answer, and for your efforts in
>> offering this PPA to the community.
>>
>> Best regards,
>>
>> Eric.
>>
>> Le vendredi 23 septembre 2016 15:49:07 UTC+2, Jan Groenewald a écrit :
>>>
>>> Hi
>>>
>>> On 23 September 2016 at 15:46, Jan Groenewald  wrote:
>>>
 were told to redistribute modified copies we must 1) remove all Ubuntu
 branding and rebuild *all*

>>>
>>>
>>> .. binaries, or 2) sign a license to redistribute to African
>>> universities only (how gracious) and they would then not be able to
>>> redistribute freely.
>>>
>>> (Sorry, accidentally cut some text).
>>>
>>> Regards,
>>> Jan
>>>
>>> --
>>>   .~.
>>>   /V\ Jan Groenewald
>>>  /( )\www.aims.ac.za
>>>  ^^-^^
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-devel+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-devel@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
>   .~.
>   /V\ Jan Groenewald
>  /( )\www.aims.ac.za
>  ^^-^^
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/sage-devel/z1XQDRt-OFs/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
  .~.
  /V\ Jan Groenewald
 /( )\www.aims.ac.za
 ^^-^^

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: crash after compiling sagemanifolds sage 7.3 (ppa aims)

[henri.gir...@gmail.com]

Ok I wait a little and try again


Le 23/09/2016 à 20:19, Jan Groenewald a écrit :
Thanks, that was the second time. Third time also failed at 10 minutes 
without buildlog.
launchpad does that sometimes but ususally 1 (or 2)  retries are 
enough. 4th retry is now showing a buildlog, and busy building, and is 
at 33 minutes, give it 30 more or so.


Regards,
Jan

On 23 September 2016 at 18:42, henri.gir...@gmail.com 
 > wrote:


I just had a look apparently it failed ?


Le 23/09/2016 à 17:11, Jan Groenewald a écrit :

Hi

If everything debian-builds OK, there will be a package here in a
few hours in the dev PPA:
https://launchpad.net/~aims/+archive/ubuntu/sagemath-dev/+packages


Watch the build
https://launchpad.net/~aims/+archive/ubuntu/sagemath-dev/+build/10947743

which take s about an hour. If successful, publishing that in the
PPA could take anything
from 5 minute to 5 hours, depending on how busy launchpad is.

Please send me feedback before I copy to the stable PPA. I can't
test that this even opens the notebook now.

Regards,
Jan

On 23 September 2016 at 16:32, Eric Gourgoulhon
mailto:egourgoul...@gmail.com>> wrote:

Hi Jan,

Thanks for your prompt and detailed answer, and for your
efforts in offering this PPA to the community.

Best regards,

Eric.

Le vendredi 23 septembre 2016 15:49:07 UTC+2, Jan Groenewald
a écrit :

Hi

On 23 September 2016 at 15:46, Jan Groenewald
 wrote:

were told to redistribute modified copies we must 1)
remove all Ubuntu branding and rebuild *all*



.. binaries, or 2) sign a license to redistribute to
African universities only (how gracious) and they would
then not be able to redistribute freely.

(Sorry, accidentally cut some text).

Regards,
Jan
-- 
  .~.

  /V\ Jan Groenewald
 /( )\ www.aims.ac.za 
 ^^-^^

-- 
You received this message because you are subscribed to the

Google Groups "sage-devel" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to sage-devel+unsubscr...@googlegroups.com
.
To post to this group, send email to
sage-devel@googlegroups.com .
Visit this group at
https://groups.google.com/group/sage-devel
.
For more options, visit https://groups.google.com/d/optout
.




-- 
  .~.

  /V\ Jan Groenewald
 /( )\ www.aims.ac.za 
 ^^-^^
-- 
You received this message because you are subscribed to a topic

in the Google Groups "sage-devel" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/sage-devel/z1XQDRt-OFs/unsubscribe
.
To unsubscribe from this group and all its topics, send an email
to sage-devel+unsubscr...@googlegroups.com
.
To post to this group, send email to sage-devel@googlegroups.com
.
Visit this group at https://groups.google.com/group/sage-devel
.
For more options, visit https://groups.google.com/d/optout
.


-- 
You received this message because you are subscribed to the Google

Groups "sage-devel" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to sage-devel+unsubscr...@googlegroups.com
.
To post to this group, send email to sage-devel@googlegroups.com
.
Visit this group at https://groups.google.com/group/sage-devel
.
For more options, visit https://groups.google.com/d/optout
.




--
  .~.
  /V\ Jan Groenewald
 /( )\ www.aims.ac.za 
 ^^-^^
--
You received this message because you are subscribed to a topic in the 
Google Groups "sage-devel" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/sage-devel/z1XQDRt-OFs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
sage-devel+unsubscr...@googlegroups.com 

Re: [sage-devel] Re: crash after compiling sagemanifolds sage 7.3 (ppa aims)

[Jan Groenewald]

Successfully Built but not published yet
https://launchpad.net/~aims/+archive/ubuntu/sagemath-dev/+packages

On 23 September 2016 at 20:33, henri.gir...@gmail.com <
henri.gir...@gmail.com> wrote:

> Ok I wait a little and try again
>
> Le 23/09/2016 à 20:19, Jan Groenewald a écrit :
>
> Thanks, that was the second time. Third time also failed at 10 minutes
> without buildlog.
> launchpad does that sometimes but ususally 1 (or 2)  retries are enough.
> 4th retry is now showing a buildlog, and busy building, and is at 33
> minutes, give it 30 more or so.
>
> Regards,
> Jan
>
> On 23 September 2016 at 18:42, henri.gir...@gmail.com <
> henri.gir...@gmail.com> wrote:
>
>> I just had a look apparently it failed ?
>>
>> Le 23/09/2016 à 17:11, Jan Groenewald a écrit :
>>
>> Hi
>>
>> If everything debian-builds OK, there will be a package here in a few
>> hours in the dev PPA:
>> https://launchpad.net/~aims/+archive/ubuntu/sagemath-dev/+packages
>> 
>>
>> Watch the build https://launchpad.net/~aims/+a
>> rchive/ubuntu/sagemath-dev/+build/10947743
>> 
>> which take s about an hour. If successful, publishing that in the PPA
>> could take anything
>> from 5 minute to 5 hours, depending on how busy launchpad is.
>>
>> Please send me feedback before I copy to the stable PPA. I can't test
>> that this even opens the notebook now.
>>
>> Regards,
>> Jan
>>
>> On 23 September 2016 at 16:32, Eric Gourgoulhon 
>> wrote:
>>
>>> Hi Jan,
>>>
>>> Thanks for your prompt and detailed answer, and for your efforts in
>>> offering this PPA to the community.
>>>
>>> Best regards,
>>>
>>> Eric.
>>>
>>> Le vendredi 23 septembre 2016 15:49:07 UTC+2, Jan Groenewald a écrit :

 Hi

 On 23 September 2016 at 15:46, Jan Groenewald  wrote:

> were told to redistribute modified copies we must 1) remove all Ubuntu
> branding and rebuild *all*
>


 .. binaries, or 2) sign a license to redistribute to African
 universities only (how gracious) and they would then not be able to
 redistribute freely.

 (Sorry, accidentally cut some text).

 Regards,
 Jan

 --
   .~.
   /V\ Jan Groenewald
  /( )\www.aims.ac.za
  ^^-^^

>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "sage-devel" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to sage-devel+unsubscr...@googlegroups.com.
>>> To post to this group, send email to sage-devel@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/sage-devel.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>>   .~.
>>   /V\ Jan Groenewald
>>  /( )\www.aims.ac.za
>>  ^^-^^
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "sage-devel" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/sage-devel/z1XQDRt-OFs/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> sage-devel+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-devel@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-devel+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-devel@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
>   .~.
>   /V\ Jan Groenewald
>  /( )\www.aims.ac.za
>  ^^-^^
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/sage-devel/z1XQDRt-OFs/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
  .~.
  /V\ Jan Groenewald
 /( )\www.aims

Re: [sage-devel] Re: crash after compiling sagemanifolds sage 7.3 (ppa aims)

[henri.gir...@gmail.com]

OK  works fine :

Writing 
/usr/lib/sagemath/local/lib/python2.7/site-packages/sage-7.3-py2.7.egg-info


real0m7.385s
user0m4.820s
sys0m1.528s

Installation of SageManifolds 0.9.1 completed!

pi@pc:/usr/lib/sagemath$ ls -al
total 932
drwxr-xr-x   8 root root   4096 sept. 24 01:21 .


Le 23/09/2016 à 20:19, Jan Groenewald a écrit :
Thanks, that was the second time. Third time also failed at 10 minutes 
without buildlog.
launchpad does that sometimes but ususally 1 (or 2)  retries are 
enough. 4th retry is now showing a buildlog, and busy building, and is 
at 33 minutes, give it 30 more or so.


Regards,
Jan

On 23 September 2016 at 18:42, henri.gir...@gmail.com 
 > wrote:


I just had a look apparently it failed ?


Le 23/09/2016 à 17:11, Jan Groenewald a écrit :

Hi

If everything debian-builds OK, there will be a package here in a
few hours in the dev PPA:
https://launchpad.net/~aims/+archive/ubuntu/sagemath-dev/+packages


Watch the build
https://launchpad.net/~aims/+archive/ubuntu/sagemath-dev/+build/10947743

which take s about an hour. If successful, publishing that in the
PPA could take anything
from 5 minute to 5 hours, depending on how busy launchpad is.

Please send me feedback before I copy to the stable PPA. I can't
test that this even opens the notebook now.

Regards,
Jan

On 23 September 2016 at 16:32, Eric Gourgoulhon
mailto:egourgoul...@gmail.com>> wrote:

Hi Jan,

Thanks for your prompt and detailed answer, and for your
efforts in offering this PPA to the community.

Best regards,

Eric.

Le vendredi 23 septembre 2016 15:49:07 UTC+2, Jan Groenewald
a écrit :

Hi

On 23 September 2016 at 15:46, Jan Groenewald
 wrote:

were told to redistribute modified copies we must 1)
remove all Ubuntu branding and rebuild *all*



.. binaries, or 2) sign a license to redistribute to
African universities only (how gracious) and they would
then not be able to redistribute freely.

(Sorry, accidentally cut some text).

Regards,
Jan
-- 
  .~.

  /V\ Jan Groenewald
 /( )\ www.aims.ac.za 
 ^^-^^

-- 
You received this message because you are subscribed to the

Google Groups "sage-devel" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to sage-devel+unsubscr...@googlegroups.com
.
To post to this group, send email to
sage-devel@googlegroups.com .
Visit this group at
https://groups.google.com/group/sage-devel
.
For more options, visit https://groups.google.com/d/optout
.




-- 
  .~.

  /V\ Jan Groenewald
 /( )\ www.aims.ac.za 
 ^^-^^
-- 
You received this message because you are subscribed to a topic

in the Google Groups "sage-devel" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/sage-devel/z1XQDRt-OFs/unsubscribe
.
To unsubscribe from this group and all its topics, send an email
to sage-devel+unsubscr...@googlegroups.com
.
To post to this group, send email to sage-devel@googlegroups.com
.
Visit this group at https://groups.google.com/group/sage-devel
.
For more options, visit https://groups.google.com/d/optout
.


-- 
You received this message because you are subscribed to the Google

Groups "sage-devel" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to sage-devel+unsubscr...@googlegroups.com
.
To post to this group, send email to sage-devel@googlegroups.com
.
Visit this group at https://groups.google.com/group/sage-devel
.
For more options, visit https://groups.google.com/d/optout
.




--
  .~.
  /V\ Jan Groenewald
 /( )\ www.aims.ac.za 
 ^^-^^
--
You received this message because you are subscribed to a topic i

[sage-devel] Re: State of sage built with clang/clang++ on OS X

[Dima Pasechnik]

On Thursday, September 15, 2016 at 9:21:34 PM UTC, François wrote:
>
> So on another thread there was talk about whether we could 
> build sage with clang+gfortran on OS X. 
> Well it is not that bad and a little push in the right place would 
> probably 
> get use 95% there. 
>
> I couldn’t build sagelib, I didn’t manage to get there. Here are the 
> packages that fail to build with clang in sage 7.4.beta4 on OS X: 
> ratpoints 
> lcalc 
> pynac 
> linbox 
> symmetrica 
> gfan 
>
> ratpoints: there is an ancient ticket (#12473). Surprisingly it is a 
> C language problem. ratpoints rely on a GNU extension to use nested 
> functions. I tried to untangle the first specimen I encountered 
> before realising that it was quite an amount of work (the nested function 
> sees and uses a number of variables from the “host” function that 
> are in scope like they were global variables, this makes things just 
> insane). 
>

I posted a preliminary fix on #12473. Please try with clang... 

>
> lcalc: is no surprise. It uses a number of obsolete features, not sure 
> how long gcc itself will build it. 
>
> pynac: 
> https://github.com/pynac/pynac/pull/192 
> https://github.com/pynac/pynac/issues/193 
> for starters. 
>
> linbox: 
> https://github.com/linbox-team/linbox/issues/39 
> more on linbox specifically later. 
>
> symmetrica: 
> In the first instance a function returning an “int” has return 
> statement with no values. Should be trivial but I didn’t 
> dig too much. 
>
> gfan: 
> some C++ constructor problem. 
>
> On most of these switching to gcc/g++ solved the problem expect for 
> linbox which revealed some tricky C++ problems with that approach. 
> linbox uses fflas-ffpack and givaro, themselves having been compiled 
> with clang++. 
> In another post I mentioned that most vendors (clang and GNU in 
> particular) 
> where following a common ABI for C++. The problem is that there is now 
> several versions of the ABI and g++ and clang++ on OS X default on 
> different one. You can get g++ to change to the right ABI but then the 
> linker get confused thinking you mix different architectures. This is 
> probably 
> solvable but show that it would be more sane to compile all C++ libraries 
> that will be included in sage with the same compiler. Stuff called by 
> pexpect 
> doesn’t matter so much, but in the list above that means lcalc, pynac and 
> linbox need to be fixed [ratpoints and symmetrica are C, gfan is used via 
> pexpect]. 
>
> I was surprised sympow didn’t make it in the list but it did compile. 
>
> François

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: [sage-support] huge virtual memory size when launching 7.3

[Jeroen Demeyer]

On 2016-09-21 16:15, Jonathan Bober wrote:

(I've swtiched from sage-support to to sage-devel.)

I can test and review.


See https://trac.sagemath.org/ticket/21582

--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.