Re: [sage-release] Sage 7.0.beta0 released

It looks like one ticket for the packages of type `script` wasn’t included then. François > On 23/12/2015, at 23:10, Sébastien Labbé wrote: > > I don't know if patchbots run make distclean but all of them report "Build > Failed" on 7.0.beta0 with the following error: > >

Re: [sage-release] Sage 7.0.beta0 released

The diff you mention is in the configure.ac, so you need to reconfigure (i.e. run SAGE_ROOT/bootstrap) On Wednesday, December 23, 2015 at 11:21:39 AM UTC+1, Sébastien Labbé wrote: > > > > On Wednesday, December 23, 2015 at 11:16:18 AM UTC+1, François wrote: >> >> It looks like one ticket for the

Re: [sage-release] Sage 7.0.beta0 released

I failed to build this latest release because of the 'R' package (see logfile [1]). It fails at this step: configure: error: --with-readline=yes (default) and headers/libs are not available I am running "debian testing", with libreadline-dev installed. Nathann [1]

Re: [sage-release] Sage 7.0.beta0 released

Build on ubuntu 16.04 with sagemanifold (daily build) Le 23/12/2015 17:13, Nathann Cohen a écrit : I failed to build this latest release because of the 'R' package (see logfile [1]). It fails at this step: configure: error: --with-readline=yes (default) and headers/libs are not available

Re: [sage-release] Sage 7.0.beta0 released

> R's own config.log, not the Sage config.log... Sorry, I misunderstood. It is there: http://www.steinertriples.fr/ncohen/tmp/config.log Nathann -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving

Re: [sage-release] Sage 7.0.beta0 released

So it looks like an ncurses problem: configure:20930: checking for rl_callback_read_char in -lreadline configure:20955: gcc -o conftest -g -O2 -L/home/ncohen/.Sage/local/lib/ -Wl,-rpath,/home/ncohen/.Sage/local/lib -Wl,-rpath,/home/ncohen/.Sage/local/lib64 conftest.c -lreadline >&5

Re: [sage-release] Sage 7.0.beta0 released

R's own config.log, not the Sage config.log... On Wednesday, December 23, 2015 at 6:05:39 PM UTC+1, Nathann Cohen wrote: > > > Can you post the config.log? It does the right thing on my machine: > > SAGE_ROOT/config.log is there: > http://www.steinertriples.fr/ncohen/tmp/config.log > >

Re: [sage-release] Sage 7.0.beta0 released

> Can you post the config.log? It does the right thing on my machine: SAGE_ROOT/config.log is there: http://www.steinertriples.fr/ncohen/tmp/config.log Thanks, Nathann -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this

Re: [sage-release] Sage 7.0.beta0 released

Can you post the config.log? It does the right thing on my machine: configure:20930: checking for rl_callback_read_char in -lreadline configure:20955: gcc -o conftest -g -O2 -L/home/vbraun/Code/sage/local/lib/ -Wl,-rpath,/home/vbraun/Code/sage/local/lib

[sage-release] Re: Sage 7.0.beta0 released

FWIW, starting from a fresh git clone, passes ptestlong with no errors on Debian testing running on Core I7 +,16 GB RAM. HTH, -- Emmanuel Charpentier Le mardi 22 décembre 2015 22:13:48 UTC+1, Volker Braun a écrit : > > As always, you can get the latest beta version from the "develop" git >

Re: [sage-release] Sage 7.0.beta0 released

Volker Braun wrote: > The "no version information available" is a consequence of using a > different library at compile and run time. In fact, we didn't pass -L > $SAGE_LOCAL/lib when linking libreadline, See #11970... ;-) When we added linking libtermcap / libtinfo to libreadline years ago

Re: [sage-release] Sage 7.0.beta0 released

libtinfo is part of ncurses, as I thought but not always built. There are report of funny things happening in ncurses and that’s probably one more. François > On 24/12/2015, at 10:03, Francois Bissey > wrote: > > Never seen that kind of output before, but

Re: [sage-release] Sage 7.0.beta0 released

ldd -r on that readline library may reveal a lack of rpath. François > On 24/12/2015, at 09:48, Nathann Cohen wrote: > >> So it looks like an ncurses problem: > > Hm O_o > > But it is using Sage's readline package, and I was compiling after a > 'distclean'

Re: [sage-release] Sage 7.0.beta0 released

Yours was a different problem. On Wednesday, December 23, 2015 at 11:17:01 PM UTC+1, Emmanuel Charpentier wrote: > > Aha ! > > I *had* problems previously with Sage's libtinfo*, which led bash to spill > a lot of warnings about "missing version information"). The conclusion of > this > thread

Re: [sage-release] Sage 7.0.beta0 released

Is libtinfo.so.5 a proper library or a symlink? And what does nm -d libtinfo.so.5 | grep tgetflag reports? François > On 24/12/2015, at 10:22, Nathann Cohen wrote: > >> and what is the output of ldd home/ncohen/.Sage/local/lib/libtinfo.so.5 > > Here it is: > >

Re: [sage-release] Sage 7.0.beta0 released

Aha ! I *had* problems previously with Sage's libtinfo*, which led bash to spill a lot of warnings about "missing version information"). The conclusion of this thread in sage-support was

Re: [sage-release] Sage 7.0.beta0 released

> ldd -r on that readline library may reveal a lack of rpath. Err Does the following "talks" to you ? :-P (d|✔)~/.Sage/local/lib$ ldd -r libreadline.so ./libreadline.so: /home/ncohen/.Sage/local/lib/libtinfo.so.5: no version information available (required by ./libreadline.so)

Re: [sage-release] Sage 7.0.beta0 released

> Is libtinfo.so.5 a proper library or a symlink? And what does > nm -d libtinfo.so.5 | grep tgetflag > reports? (d|✔)~/.Sage/local/lib$ ls -lsh libtinfo.so.5 0 lrwxrwxrwx 1 ncohen ncohen 15 Dec 23 09:38 libtinfo.so.5 -> libtinfo.so.5.9 (d|✔)~/.Sage/local/lib$ nm libtinfo.so.5 | grep tgetflag

Re: [sage-release] Sage 7.0.beta0 released

> So it looks like an ncurses problem: Hm O_o But it is using Sage's readline package, and I was compiling after a 'distclean' O_o Nathann -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop

Re: [sage-release] Sage 7.0.beta0 released

Wrong. Additional directories in the Sage root are removed too, but not git repo directories. On Wed, Dec 23, 2015 at 9:00 AM Ralf Stephan wrote: > On Tue, Dec 22, 2015 at 11:16 PM Volker Braun > wrote: > >> Thats because "make distclean" uses Sage's