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

> On Dec 22, 2015, at 16:13, Volker Braun wrote: > > As always, you can get the latest beta version from the "develop" git branch. > Alternatively, the self-contained source tarball is at > http://www.sagemath.org/download-latest.html Built from the tarball on OS X 10.10.5 (Quad core Core i7)

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

This is now http://trac.sagemath.org/ticket/19776 On Thursday, December 24, 2015 at 11:20:19 AM UTC+1, Volker Braun wrote: > > I think we should just globally add -L${SAGE_LOCAL}/lib to LDFLAGS, there > shouldn't be any reason to prefer system libraries over libraries in Sage > -- You received

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

> I think we should just globally add -L${SAGE_LOCAL}/lib to LDFLAGS, there > shouldn't be any reason to prefer system libraries over libraries in Sage Sounds right. Now, it is not that I don't want to create the ticket/branch, but I am perfectly aware that I do not understand the consequences of

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

I think we should just globally add -L${SAGE_LOCAL}/lib to LDFLAGS, there shouldn't be any reason to prefer system libraries over libraries in Sage -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receivin

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

> I added -L${SAGE_LOCAL}/lib to the spkg-install of both > readline and ncurses (for good measure) and this resolves > the linking problem I had with ncurses on OpenSuSE Leap. Thanks ! Adding: LDFLAGS="$LDFLAGS -L${SAGE_LOCAL}/lib" to SAGE_ROOT/build/pkgs/r/spkg-install solved my problem.

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

I added -L${SAGE_LOCAL}/lib to the spkg-install of both readline and ncurses (for good measure) and this resolves the linking problem I had with ncurses on OpenSuSE Leap. On Thu, Dec 24, 2015 at 4:38 AM leif wrote: > Volker Braun wrote: > > The "no version information available" is a consequence

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 (beca

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

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 t

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

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, I'm guessing this causes us to pick up the versioned symbol names from the system libtinfo: gcc -shared -Wl,-soname,

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

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: > > (d|✔)~/.Sage/local/lib$ ldd lib

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

> and what is the output of ldd home/ncohen/.Sage/local/lib/libtinfo.so.5 Here it is: (d|✔)~/.Sage/local/lib$ ldd libtinfo.so.5 linux-vdso.so.1 (0x7fffa4944000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f648000) /lib64/ld-linux-x86-64.so.2 (0x7f6444a21000) Nathann -- You

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

and what is the output of ldd home/ncohen/.Sage/local/lib/libtinfo.so.5 On Wednesday, December 23, 2015 at 9:55:33 PM UTC+1, Nathann Cohen wrote: > > > 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

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 something is clearly funny about >

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

Never seen that kind of output before, but something is clearly funny about libtinfo and that’s the cause of the problem. I don’t know where libtinfo is coming from however. I wonder if there is something circular going on. François > On 24/12/2015, at 09:55, Nathann Cohen wrote: > >> ldd -r o

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) linux-vdso.so.1

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' O_o > > Nathann > > -- >

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 receivi

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 /home/nc

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

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

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 g

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 -Wl,-rpath,/home/vbraun/Code/sage/local

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

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] http://www.steinertriples.

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

On Wednesday, December 23, 2015 at 11:16:18 AM UTC+1, François wrote: > > It looks like one ticket for the packages of type `script` wasn’t included > then. > But I can see that http://trac.sagemath.org/ticket/19427 merged in sage-7.0.beta0 contains the diff: - echo >&2 "The content of \"$PK

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: > > checking if g++ accep

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

GP doesn't work (am I the only one with this problem?) due to rpath trouble. See http://trac.sagemath.org/ticket/19764 -- 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 ema

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

Ncurses fails to build with gcc-5.2.1: gcc -DHAVE_CONFIG_H -I../ncurses -I../../ncurses -I. -I../include -I../../ncurses/.. /include -I/home/ralf/sage/local/include -D_GNU_SOURCE -DNDEBUG -O2 --param max-inl ine-insns-single=1200 -fPIC -c ../../ncurses/base/lib_getstr.c -o ../obj_s/lib_getst r.o _

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 Python which doesn't work. Run >> "git clean

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

On Tue, Dec 22, 2015 at 11:16 PM Volker Braun wrote: > Thats because "make distclean" uses Sage's Python which doesn't work. Run > "git clean -f -d -x" which doesn't use any Sage internals. > Note that this does also delete ALL files not from Sage in the Sage root directory, not however such dir

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

On SageMathCloud, built from source, passes long tests ("ptestlong"). Development Images and Build Logs available at: https://cloud.sagemath.com/projects/53b77207-8614-4086-a032-432af4b4cdbd/files/sage-dev-images/ -- You received this message because you are subscribed to the Google Groups "sag

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

Thats because "make distclean" uses Sage's Python which doesn't work. Run "git clean -f -d -x" which doesn't use any Sage internals. On Tuesday, December 22, 2015 at 10:44:14 PM UTC+1, Jeroen Demeyer wrote: > > On 2015-12-22 22:13, Volker Braun wrote: > > You need to compile from scratch > >

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

trac #19641 would be “causing” this. > On 23/12/2015, at 10:44, Jeroen Demeyer wrote: > > On 2015-12-22 22:13, Volker Braun wrote: >> You need to compile from scratch > > Could you elaborate a bit on why this is the case. > > I tried not doing "make distclean" and I immediately got > > Traceba

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

On 2015-12-22 22:13, Volker Braun wrote: You need to compile from scratch Could you elaborate a bit on why this is the case. I tried not doing "make distclean" and I immediately got Traceback (most recent call last): File "/usr/local/src/sage-config/build/bin/sage-download-file", line 25,

[sage-release] Sage 7.0.beta0 released

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html As mentioned before, there are no incremental updates from 6.x. You need to compile from scratch, e.g. after cleaning