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

2015-10-01 Thread leif
Andrey Novoseltsev wrote: > Not sure if has surfaced already, but after make distclean the build > with tests fails at > > ... > Running the test suite for gf2x-1.1.p1... Which version of GCC, CPU? -leif > make[3]: Entering directory >

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

2015-10-01 Thread Andrey Novoseltsev
On Thursday, 1 October 2015 12:03:41 UTC-6, leif wrote: > > Andrey Novoseltsev wrote: > > Not sure if has surfaced already, but after make distclean the build > > with tests fails at > > > > ... > > Running the test suite for gf2x-1.1.p1... > > Which version of GCC, CPU? >

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

2015-10-01 Thread Andrey Novoseltsev
On Thursday, 1 October 2015 12:16:37 UTC-6, Andrey Novoseltsev wrote: > > Will retry and see if it is reproducible. > > It was reproducible (at least once) if I do "make distclean" first. Doing "make" after the failure went fine (stuck on SageTeX). -- You received this message because you

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

2015-09-30 Thread Jeroen Demeyer
On 2015-09-28 20:00, 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? Should be fixed upstream and in Sage at

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: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:

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: ...

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

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

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

2015-09-28 Thread Sébastien Labbé
On Ubuntu 14.04 64 bit, Using

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

2015-09-25 Thread strogdon
The current rc0 builds here on my gentoo box. However, I'm having difficulty merging tickets with rc0. Yesterday, with 6.9.beta7 I was testing a branch with trac #19272 merged and everything was fine. Today, after pulling 6.9.rc0 and building it I created a new branch for trac #19272 and

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

2015-09-25 Thread strogdon
Nevermind! I missed the new ".configure" before "make". On Friday, September 25, 2015 at 4:09:58 PM UTC-5, strogdon wrote: > > The current rc0 builds here on my gentoo box. However, I'm having > difficulty merging tickets with rc0. Yesterday, with 6.9.beta7 I was > testing a branch with trac