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

[Justin C. Walker]

> 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).  No problems and 
all tests (‘ptestlong’) passed.

Justin

--
Justin C. Walker, Curmudgeon at Large
Director
Institute for the Enhancement of the Director's income
---
--
They said it couldn't be done, but sometimes,
it doesn't work out that way.
 - Casey Stengel
--



-- 
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

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

Should I create a branch that does that ?

Nathann

-- 
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Volker Braun]

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 receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Volker Braun]

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 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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

> 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 something
like that S if you don't mind I prefer to not be the one who
does it ^^;

Nathann

-- 
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Francois Bissey]

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++ accepts -dumpversion option... yes
> checking g++ version... 4.7.3
> checking for sqrt in -lm... yes
> checking package versions... 
> The content of "/home/worker/sage-patchbot/build/pkgs/r_jupyter/type" must be 
> 'base', 'standard', 'optional', 'experimental' or 'pip'
> Apply -- 7 seconds
> Traceback (most recent call last):
>   File "/home/worker/sage-patchbot/local/bin/patchbot/patchbot.py", line 940, 
> in test_a_ticket
> do_or_die('./configure')
>   File "/home/worker/sage-patchbot/local/bin/patchbot/util.py", line 182, in 
> do_or_die
> raise exn_class("{} {}".format(res, cmd))
> Exception: 256 ./configure
> 2015-12-23 02:53:04
> 10 seconds
> 
> 
> See for instance:
> http://patchbot.sagemath.org/ticket/19620/
> 
> 
> On Tuesday, December 22, 2015 at 10:13:48 PM UTC+1, 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
> 
> As mentioned before, there are no incremental updates from 6.x. You need to 
> compile from scratch, e.g. after cleaning with "make distclean" or "git clean 
> -f -d -x". If you are still working on tickets based on 6.x then you might 
> want to use a separate git tree for sage 7.
> 
> d83dab1 Updated Sage version to 7.0.beta0
> 322ee09 Trac #19705: Add ppc64le support to config.guess
> 413b496 Trac #19703: Update config.guess in bzip2
> 7d72b46 Trac #19697: Posets: Add is_eulerian
> e1d06a7 Trac #19695: Remove duplicate code in cachefunc.pyx
> 6f9ec67 Trac #19694: Deprecate CachedFunction.get_cache()
> b0bc355 Trac #19691: Add groebner_basis() method for univariate polynomials
> 1000a45 Trac #19688: Much fast divisors using PARI divisorsu
> 62487a2 Trac #19571: Register Sage classes in numbers abc
> 64adf70 Trac #19487: Support .zip upstream/ files
> 4b95f5e Trac #19137: Use inverse_series_trunc in power series
> 70a077c Trac #19097: Refactor run_[revised]_simplex_method; add 
> run_dual_[revised]_simplex_method
> 8b250a0 Trac #19001: Conic morphism creation fails on some base fields
> 0b9c2b3 Trac #19731: Upgrade NTL
> 816a955 Trac #19744: Update to pynac-0.5.3
> f2d60d3 Trac #19693: Update 4ti2 to version 1.6.7
> 4fd7966 Trac #19692: Upgrade R to 3.2.3
> f5afd66 Trac #19638: upgrade rpy2 to 2.7.5
> dc1b1c2 Trac #19734: Maxima: use newer version of config.guess
> acb2a37 Trac #19732: ECL: use newer version of config.guess
> 1807dc6 Trac #19729: Rename boehm_gc to gc and upgrade to latest upstream
> 30d3ffb Trac #19728: givaro: use newer version of config.guess
> 313256e Trac #19727: gf2x: use newer version of config.guess
> 1c6068f Trac #19726: GAP: use newer version of config.guess
> 75de776 Trac #19725: lrcalc: use newer version of config.guess
> d917694 Trac #19724: ECM: use newer version of config.guess
> 171615c Trac #19723: planarity: use newer version of config.guess
> 3432fcf Trac #19718: cddlib: use newer version of config.guess
> 78bc721 Trac #19717: Allow tachyon to install on ppc64le
> 8c0b8c0 Trac #19716: MPFI: use newer version of config.guess
> 729286a Trac #19714: ZeroMQ: use newer version of config.guess
> abde87d Trac #19713: GLPK: use newer version of config.guess
> de8d57b Trac #19711: SQLite: use newer version of config.guess
> 73f8e6a Trac #18844: updating  upstream data in SPKG.txt of boehm_gc
> c13a6f5 Trac #19702: Upgrade GNU patch
> 0141205 Trac #19709: Upgrade MPC
> 6bdce5c Trac #19708: Upgrade MPFR
> a4ec8cc Trac #19427: Jupyter R kernel
> c12ef20 Trac #10295: Upgrade and optimize pexpect
> 3524b13 Trac #19616: Update sagenb
> 3296bb3 Trac #19671: Ignore all exceptions in ._sage_doc_ attribute access
> 9efb8a6 Trac #19641: Remove (DY)LD_LIBRARY_PATH
> cabcca6 Trac #19699: Update FlintQS
> a1b60f2 Updated Sage version to 6.10
> 
> 
> -- 
> 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...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Volker Braun]

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 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 \"$PKG_TYPE_FILE\" must be 'base', 'standard', 
> 'optional', 'experimental' or 'pip'"
> + echo >&2 "The content of \"$PKG_TYPE_FILE\" must be 'base', 'standard', 
> 'optional', 'experimental', 'script', or 'pip'"
>
> Therefore, I guess patchbot are not running sage-7.0.beta0 cleanly...
>

-- 
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

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.fr/ncohen/tmp/r-3.2.3.p0.log

On 23 December 2015 at 12:52, Volker Braun  wrote:
> 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 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 \"$PKG_TYPE_FILE\" must be 'base', 'standard',
>> 'optional', 'experimental' or 'pip'"
>> + echo >&2 "The content of \"$PKG_TYPE_FILE\" must be 'base', 'standard',
>> 'optional', 'experimental', 'script', or 'pip'"
>>
>> Therefore, I guess patchbot are not running sage-7.0.beta0 cleanly...
>
> --
> 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...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Henri Girard]

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

I am running "debian testing", with libreadline-dev installed.

Nathann

[1] http://www.steinertriples.fr/ncohen/tmp/r-3.2.3.p0.log

On 23 December 2015 at 12:52, Volker Braun  wrote:

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 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 \"$PKG_TYPE_FILE\" must be 'base', 'standard',
'optional', 'experimental' or 'pip'"
+ echo >&2 "The content of \"$PKG_TYPE_FILE\" must be 'base', 'standard',
'optional', 'experimental', 'script', or 'pip'"

Therefore, I guess patchbot are not running sage-7.0.beta0 cleanly...

--
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


--
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

> 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 emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Volker Braun]

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/ncohen/.Sage/local/lib//libreadline.so: undefined reference to 
`tgetflag@NCURSES_TINFO_5.0.19991023'
/home/ncohen/.Sage/local/lib//libreadline.so: undefined reference to 
`UP@NCURSES_TINFO_5.0.19991023'
/home/ncohen/.Sage/local/lib//libreadline.so: undefined reference to 
`tputs@NCURSES_TINFO_5.0.19991023'
/home/ncohen/.Sage/local/lib//libreadline.so: undefined reference to 
`tgetnum@NCURSES_TINFO_5.0.19991023'
/home/ncohen/.Sage/local/lib//libreadline.so: undefined reference to 
`BC@NCURSES_TINFO_5.0.19991023'
/home/ncohen/.Sage/local/lib//libreadline.so: undefined reference to 
`tgetstr@NCURSES_TINFO_5.0.19991023'
/home/ncohen/.Sage/local/lib//libreadline.so: undefined reference to 
`tgetent@NCURSES_TINFO_5.0.19991023'
/home/ncohen/.Sage/local/lib//libreadline.so: undefined reference to 
`PC@NCURSES_TINFO_5.0.19991023'
/home/ncohen/.Sage/local/lib//libreadline.so: undefined reference to 
`tgoto@NCURSES_TINFO_5.0.19991023'
collect2: error: ld returned 1 exit status
configure:20955: $? = 1




On Wednesday, December 23, 2015 at 6:13:29 PM UTC+1, Nathann Cohen wrote:
>
> > 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 emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Volker Braun]

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, 
>
> Nathann 
>

-- 
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

> 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 group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Volker Braun]

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/lib64  conftest.c -lreadline   >&5
configure:20955: $? = 0


On Wednesday, December 23, 2015 at 5:13:23 PM UTC+1, Nathann Cohen wrote:
>
> 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.fr/ncohen/tmp/r-3.2.3.p0.log 
>
> On 23 December 2015 at 12:52, Volker Braun  > wrote: 
> > 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 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 \"$PKG_TYPE_FILE\" must be 'base', 
> 'standard', 
> >> 'optional', 'experimental' or 'pip'" 
> >> + echo >&2 "The content of \"$PKG_TYPE_FILE\" must be 'base', 
> 'standard', 
> >> 'optional', 'experimental', 'script', or 'pip'" 
> >> 
> >> Therefore, I guess patchbot are not running sage-7.0.beta0 cleanly... 
> > 
> > -- 
> > 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...@googlegroups.com . 
> > To post to this group, send email to sage-r...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/sage-release. 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[leif]

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
(because of R btw.), we intentionally omitted -L${SAGE_LOCAL}/lib, since
Sage only shipped with a static libtermcap to that time, and we *wanted*
to use the system's libraries (ncurses-dev was a prerequisite).

Apparently nobody cared to change that when ncurses became a Sage
standard package (despite the comments on that the same ticket, #14405,
removed from spkg-install).

Just saying...


-leif


> I'm guessing this causes us to
> pick up the versioned symbol names from the system libtinfo:
> 
> gcc -shared -Wl,-soname,libreadline.so.6.3
> -Wl,-rpath,/home/vbraun/Code/sage/local/lib -Wl,-rpath,/home/v
> braun/Code/sage/local/lib64  -Wl,-rpath,/home/vbraun/Code/sage/local/lib
> -Wl,-soname,`basename libreadlin
> e.so.6.3 .3` -o libreadline.so.6.3 readline.so vi_mode.so funmap.so
> keymaps.so parens.so search.so rltty.
> so complete.so bind.so isearch.so display.so signals.so util.so kill.so
> undo.so macro.so input.so callbac
> k.so terminal.so text.so nls.so misc.so history.so histexpand.so
> histfile.so histsearch.so shell.so mbuti
> l.so tilde.so colors.so parse-colors.so xmalloc.so xfree.so compat.so
> -ltinfo
> 
> 
> 
> 
> 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 -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 (0x7ffd3afae000)
> libtinfo.so.5 => /home/ncohen/.Sage/local/lib/libtinfo.so.5
> (0x7fde9a7fe000)
> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fde9a45a000)
> /lib64/ld-linux-x86-64.so.2 (0x7fde9ac7c000)
> 
> Nathann

-- 
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Francois Bissey]

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 
> 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 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 (0x7ffd3afae000)
>> libtinfo.so.5 => /home/ncohen/.Sage/local/lib/libtinfo.so.5 
>> (0x7fde9a7fe000)
>> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fde9a45a000)
>> /lib64/ld-linux-x86-64.so.2 (0x7fde9ac7c000)
>> 
>> Nathann
>> 
>> -- 
>> 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...@googlegroups.com.
>> To post to this group, send email to sage-release@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-release.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> 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...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Francois Bissey]

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
> 
> -- 
> 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...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Volker Braun]

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 
> 
>  
> in sage-support was that it was a collision between Sage's and system's 
> (Debian testing on amd64) libraries.
>
> I found that moving local/lib/libtinfo* out of the way allowed me to run 
> Sage without those pesky warnings.
>
> Nathaan, could you try to move these libraries out of the way and try to 
> install R ?
>
> HTH,
>
> --
> Emmanuel Charpentier
>
>
> Le mercredi 23 décembre 2015 22:08:46 UTC+1, François a écrit :
>>
>> 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 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 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 (0x7ffd3afae000) 
>> >> libtinfo.so.5 => /home/ncohen/.Sage/local/lib/libtinfo.so.5 
>> (0x7fde9a7fe000) 
>> >> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fde9a45a000) 
>> >> /lib64/ld-linux-x86-64.so.2 (0x7fde9ac7c000) 
>> >> 
>> >> Nathann 
>> >> 
>> >> -- 
>> >> 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...@googlegroups.com. 
>> >> To post to this group, send email to sage-r...@googlegroups.com. 
>> >> Visit this group at https://groups.google.com/group/sage-release. 
>> >> For more options, visit https://groups.google.com/d/optout. 
>> > 
>> > -- 
>> > 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...@googlegroups.com. 
>> > To post to this group, send email to sage-r...@googlegroups.com. 
>> > Visit this group at https://groups.google.com/group/sage-release. 
>> > For more options, visit https://groups.google.com/d/optout. 
>>
>>

-- 
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Francois Bissey]

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 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 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...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Emmanuel Charpentier]

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 that it was a collision between Sage's and system's 
(Debian testing on amd64) libraries.

I found that moving local/lib/libtinfo* out of the way allowed me to run 
Sage without those pesky warnings.

Nathaan, could you try to move these libraries out of the way and try to 
install R ?

HTH,

--
Emmanuel Charpentier


Le mercredi 23 décembre 2015 22:08:46 UTC+1, François a écrit :
>
> 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 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 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 (0x7ffd3afae000) 
> >> libtinfo.so.5 => /home/ncohen/.Sage/local/lib/libtinfo.so.5 
> (0x7fde9a7fe000) 
> >> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fde9a45a000) 
> >> /lib64/ld-linux-x86-64.so.2 (0x7fde9ac7c000) 
> >> 
> >> Nathann 
> >> 
> >> -- 
> >> 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...@googlegroups.com . 
> >> To post to this group, send email to sage-r...@googlegroups.com 
> . 
> >> Visit this group at https://groups.google.com/group/sage-release. 
> >> For more options, visit https://groups.google.com/d/optout. 
> > 
> > -- 
> > 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...@googlegroups.com . 
> > To post to this group, send email to sage-r...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/sage-release. 
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

> 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 (0x7ffd3afae000)
libtinfo.so.5 => /home/ncohen/.Sage/local/lib/libtinfo.so.5 (0x7fde9a7fe000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fde9a45a000)
/lib64/ld-linux-x86-64.so.2 (0x7fde9ac7c000)

Nathann

-- 
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

> 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
00013430 T tgetflag

(I removed the -d from 'nm -d', as it complained that -d was an invalid option)

Nathann

-- 
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Nathann Cohen]

> 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 receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Ralf Stephan]

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

-- 
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Jeroen Demeyer]

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, in 

import sage_bootstrap
  File 
"/usr/local/src/sage-config/build/bin/../sage_bootstrap/__init__.py", 
line 2, in 

from sage_bootstrap.config import Configuration
  File 
"/usr/local/src/sage-config/build/bin/../sage_bootstrap/config.py", line 
34, in 

import logging
  File 
"/usr/local/src/sage-config/local/lib/python/logging/__init__.py", line 
26, in 
import sys, os, time, cStringIO, traceback, warnings, weakref, 
collections

ImportError: No module named time

--
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Francois Bissey]

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
> 
> Traceback (most recent call last):
>  File "/usr/local/src/sage-config/build/bin/sage-download-file", line 25, in 
> 
>import sage_bootstrap
>  File "/usr/local/src/sage-config/build/bin/../sage_bootstrap/__init__.py", 
> line 2, in 
>from sage_bootstrap.config import Configuration
>  File "/usr/local/src/sage-config/build/bin/../sage_bootstrap/config.py", 
> line 34, in 
>import logging
>  File "/usr/local/src/sage-config/local/lib/python/logging/__init__.py", line 
> 26, in 
>import sys, os, time, cStringIO, traceback, warnings, weakref, collections
> ImportError: No module named time
> 
> -- 
> 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...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
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...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Rob Beezer]

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 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.