Re: [sage-release] Sage 6.9.rc0 released

2015-09-28 Thread William Stein
On Monday, September 28, 2015, Volker Braun wrote: > Hmm but /usr/lib/x86_64-linux-gnu/libpari-gmp-tls.so.2.7.2 brings just a > slightly different version of Pari's concat. It may very well be that it > doesn't trigger libkpathsea crashing but thats just by chance; the symbol > conflict is still

Re: [sage-release] Re: Sage 6.9.rc0 released

2015-09-28 Thread Volker Braun
Hmm but /usr/lib/x86_64-linux-gnu/libpari-gmp-tls.so.2.7.2 brings just a slightly different version of Pari's concat. It may very well be that it doesn't trigger libkpathsea crashing but thats just by chance; the symbol conflict is still there. The correct fix is to not export concat; neither

Re: [sage-release] Re: Sage 6.9.rc0 released

2015-09-28 Thread William Stein
On Mon, Sep 28, 2015 at 11:28 AM, Volker Braun wrote: > Symbol collision. Unless TeX's libkpathsea really intends to use concat() > from Pari... That makes sense. Basically you're noticing this part of the traceback: ... /projects/sage/sage-6.9/local/lib/libpari-gmp-2.8.so.0(concat+0x830)[0x7f5

Re: [sage-release] Re: Sage 6.9.rc0 released

2015-09-28 Thread Volker Braun
Symbol collision. Unless TeX's libkpathsea really intends to use concat() from Pari... -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@

Re: [sage-release] Re: Sage 6.9.rc0 released

2015-09-28 Thread William Stein
On Mon, Sep 28, 2015 at 11:00 AM, William Stein wrote: > In Sage-6.7 this library (which is *pure python*) works well: > >https://github.com/datasift > > In Sage-6.9.beta6 (for me) this library crashes with the following > weird traceback. Any ideas? Two additional points: (1) If I just run

Re: [sage-release] Re: Sage 6.9.rc0 released

2015-09-28 Thread William Stein
In Sage-6.7 this library (which is *pure python*) works well: https://github.com/datasift In Sage-6.9.beta6 (for me) this library crashes with the following weird traceback. Any ideas? (sage-sh) [m 4a5f054258734eeda85ca18c706e8bcd@compute4-us:tmp$ which [Kpython Python 2.7.9 (default,

[sage-release] Re: Sage 6.9.rc0 released

2015-09-28 Thread Volker Braun
Fixed in #19294 On Monday, September 28, 2015 at 4:48:21 PM UTC+2, Sébastien Labbé wrote: > > On Ubuntu 14.04 64 bit, > > Using > --optional=arb,benzene,bliss,buckygen,cbc,coxeter3,cryptominisat,database_cremona_ellcurve,database_gap,database_odlyzko_zeta,database_pari,database_stein_watkins,data

[sage-release] Re: Sage 6.9.rc0 released

2015-09-28 Thread Sébastien Labbé
On Ubuntu 14.04 64 bit, Using --optional=arb,benzene,bliss,buckygen,cbc,coxeter3,cryptominisat,database_cremona_ellcurve,database_gap,database_odlyzko_zeta,database_pari,database_stein_watkins,database_symbolic_data,dot2tex,gambit,gap_packages,gcc,gdb,mcqd,modular_decomposition,mpir,nauty,plantri

Re: [sage-release] Sage 6.9.rc0 released

2015-09-28 Thread Clemens Heuberger
I recompiled 6.9.beta7 and 6.9.rc0 last night one after the other on the same machine with negligible other load. 6.9.beta7: 81 minutes 6.9.rc0:173 minutes (make -j4 with 8 GB RAM, linux 64 bit). I currently do not have a breakdown as "time" would give it (because I did not know that this