Re: [sage-devel] Re: Python3?

['Julien Puydt' via sage-devel]

Hi,

On 19/01/2017 08:47, Frédéric Chapoton wrote:


The problem with cmp is quite hard, and it seems that every instance of
cmp() must be handled separately. I have gained some experience on the
subject, but given the lack of reviewers, this implies a very slow pace.
This cmp problem should be the last remaining thing to handle before
reaching 1A) and maybe even 1B)


is there some place with a good summary of the cmp situation, and can 
you point at some patches showing how the matter is fixed?


Thanks,

Snark on #debian-science

--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Python3?

[Frédéric Chapoton]

Hello,

let me try to summarize : we are still *quite far* from being python3 
compatible.

There are two main milestones we must reach:

1)  being able to build sage with python3 ;
(with substeps: 1A) being able to cythonize all pyx files / 1B) being able 
to compile all pyx files) 1C) being able to build all py files.

2) having all doctests pass

Currently, progress is very slowly being made on 1) and some changes are 
made in parallel (in a blind way) for 2)

Concerning 1), I would say cmp and unicode are the main remaining problems. 
Integer division has almost been tackled, but not quite.

The problem with cmp is quite hard, and it seems that every instance of 
cmp() must be handled separately. I have gained some experience on the 
subject, but given the lack of reviewers, this implies a very slow pace. 
This cmp problem should be the last remaining thing to handle before 
reaching 1A) and maybe even 1B)

For 1C), the cmp problem has not been considered yet, but it is *huge*.

Unicode problem has almost not been looked at either. I just had a quick 
look at #14153.

Concerning having doctests pass 2), some work has already been done, but 
given that we are not able to build, this is done without any check, which 
is bad. Here, we are trying (in the dark) to prepare things for when build 
will happen.

Some general comments : I have been told to make progress by small steps, 
so using many tickets. This is maybe better for stability, but implies that 
every single move takes a long time to enter sage: review and closing may 
take months. Very often, I must stop working on python3, because there are 
already many positively reviewed tickets, and only much later they willl be 
closed. I need them to be cleaned up to have a clear view of the situation.

Another problem is regression. I have made patchbot plugins to try and 
prevent incompatible code to enter sage again. This is not sufficient. We 
need to have the doctest framework itself check that there is no bad print 
and a few other solved issues. I have required help to do that, but nobody 
stepped in.

I would like to thank here the people that have been tirelessly refering so 
many of the python3 tickets, in particular Travis, Jeroen and Jori. If some 
other people are interested, reviewing tickets would be helpful. Or even 
working on the remaining issues. I did not want to do all this just me 
alone...

Frederic


Le jeudi 19 janvier 2017 03:36:01 UTC+1, William a écrit :
>
> Hi, 
>
> Does anybody have an "executive summary" of the status of Sage and 
> Python3?   Many people keep asking me,  and I don't have a good 
> answer. 
>
>  -- William 
>
> -- 
> William (http://wstein.org) 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Python3?

[Travis Scrimshaw]

Frédéric has been working on getting stuff Python3 compatible. When he 
wakes up, he probably will give us an assessment. I believe he is able to 
get Sage to compile with Python3 with perhaps a few small tickets.

Best,
Travis

On Wednesday, January 18, 2017 at 10:09:50 PM UTC-6, David Roe wrote:
>
> I haven't been working on it, but relevant metatickets:
> https://trac.sagemath.org/ticket/15530
> https://trac.sagemath.org/ticket/15980
> https://trac.sagemath.org/ticket/16052
>
> I will defer to people who have been actively working on it, but my 
> impression is that there has been a great deal of progress, though there 
> are some aspects which will still take a lot of work (revising comparison, 
> integer division, and strings vs unicode among other issues).
> David
>
>
> On Wed, Jan 18, 2017 at 9:35 PM, William Stein  > wrote:
>
>> Hi,
>>
>> Does anybody have an "executive summary" of the status of Sage and
>> Python3?   Many people keep asking me,  and I don't have a good
>> answer.
>>
>>  -- William
>>
>> --
>> William (http://wstein.org)
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to sage-devel+...@googlegroups.com .
>> To post to this group, send email to sage-...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Python3?

[David Roe]

I haven't been working on it, but relevant metatickets:
https://trac.sagemath.org/ticket/15530
https://trac.sagemath.org/ticket/15980
https://trac.sagemath.org/ticket/16052

I will defer to people who have been actively working on it, but my
impression is that there has been a great deal of progress, though there
are some aspects which will still take a lot of work (revising comparison,
integer division, and strings vs unicode among other issues).
David


On Wed, Jan 18, 2017 at 9:35 PM, William Stein  wrote:

> Hi,
>
> Does anybody have an "executive summary" of the status of Sage and
> Python3?   Many people keep asking me,  and I don't have a good
> answer.
>
>  -- William
>
> --
> William (http://wstein.org)
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Python3?

[William Stein]

Hi,

Does anybody have an "executive summary" of the status of Sage and
Python3?   Many people keep asking me,  and I don't have a good
answer.

 -- William

-- 
William (http://wstein.org)

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: SendGrid (trac emails) issue

[Dima Pasechnik]

On Sunday, January 15, 2017 at 3:04:41 PM UTC, Michael Orlitzky wrote:
>
> Some of my trac emails are still going missing. In the last case at 
> least, this is because the message failed temporarily, and SendGrid 
> never retried it (they're required to do by the RFCs). This is the 
> original attempt, 
>
>   Jan  2 20:04:10 mx1 postfix/postscreen[5269]: NOQUEUE: reject: RCPT 
>   from [167.89.100.166]:32175: 450 4.3.2 Service currently unavailable; 
>   from= >, 
>   to=, proto=ESMTP, 
>   helo= 
>
> and there are none afterwards. Can someone with access to the SendGrid 
> account please open a support ticket? I've tried postmaster@ and abuse@ 
> with no success, and their "Contact Us" page doesn't do that. 
>

Open a ticket? 
OK, done, it is number #887046
We will see what they say...

Dima

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: R fails to compile

[Samuel Lelievre]

Tue 2017-01-17 02:24:54 UTC, Rob Gross:

> I tried to upgrade to 7.5.1 on several different Macs which I thought had 
identical software.
>
> However, on one of them, R failed to compile, with the error:
>
>   installing 'sysdata.rda'
> dyld: Symbol not found: __libiconv_version
>   Referenced from: 
/Users/gross/sage-7.0/local/var/tmp/sage/build/r-3.2.4-revised.p0/src/lib/libR.dylib
>   Expected in: flat namespace
>  in 
/Users/gross/sage-7.0/local/var/tmp/sage/build/r-3.2.4-revised.p0/src/lib/libR.dylib
> /bin/sh: line 1: 22794 Doneecho 
"tools:::sysdata2LazyLoadDB(\"./R/sysdata.rda\",\"../../../library/tools/R\")"
>  22795 Abort trap: 6   | R_DEFAULT_PACKAGES=NULL LC_ALL=C 
../../../bin/R --vanilla --slave
>
> Any ideas?
>
> Thanks.--Rob

Just to make sure, you are working in a directory called

 /Users/gross/sage-7.0

but you have checked out the sources for version 7.5.1 using git,
is that right?

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Current Maxima version

[Emmanuel Charpentier]

I added a reminder about this problem on #22191...

HTH,

--
Emmanuel Charpentier

Le mercredi 18 janvier 2017 19:47:37 UTC+1, Dima Pasechnik a écrit :
>
> I can confirm that this example also works on Maxima 5.39.0 running on 
> SBCL 1.3.12.
> (I thought for a moment that it's a regression from 5.38.1 to 5.39.0...)
>
> I suspect this could be fixed by an upgrade of ECL to 16.1.3 - something 
> that is dealt with on  
> #22191 and appears to be tricky.
>
>
> On Monday, November 28, 2016 at 9:26:19 PM UTC, Paul Masson wrote:
>>
>> The version of Maxima that ships with Sage is 5.35.1 from December 2014, 
>> while the most recent version is 5.38.1 from May 2016.
>>
>> Is there a compelling reason not to upgrade this package? Surely some of 
>> the Maxima bug fixes will be relevant to Sage.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] optional packages in multiple source builds

[Greg Marks]

Dear SAGE Developers,

I was pleased to find that, when building SAGE from source on more
than one computer, one can copy a compressed package file to the
"upstream" SAGE subdirectory and it will be automatically detected
when installing optional packages.  As some of the compressed package
files are rather large, this saves a lot of time for people with slow
Internet connections who might otherwise download the same package file
repeatedly, on each computer.  Perhaps this little tip might be worth
mentioning in the README.md file?

Sincerely,
Greg Marks

   --
  | Greg Marks   |
  | Department of Mathematics and Statistics |
  | St. Louis University |
  | St. Louis, MO 63103-2007 |
  | U.S.A.   |
  |  |
  | Phone: (314)977-7206 |
  | PGP encryption public key ID: 0x53F269E8 |
  | Web: http://gmarks.org   |
   --

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Our SSL serial drama-cum-cliffhanger

[Dima Pasechnik]

On Wednesday, January 18, 2017 at 1:20:20 PM UTC, Emmanuel Charpentier 
wrote:
>
> I'm not sure to understand the ticket. Does that means that OS X Sage will 
> depend on Apple's SSL library ? Or depend on a systemwide OpenSSL ? Or am I 
> mistaken entirely ?
>
> Apple still sneakily ships OpenSSL headers in XCode, for some sort of 
upgrading tools, I guess.
The location is unstable, though, it chnages from one version of XCode to 
another :-)

Using homebrew to build Sage on OSX isn't well-explored, IMHO. It might 
work, given some effort is made.

 

> --
> Emmanuel Charpentier
>
> Le lundi 16 janvier 2017 21:07:40 UTC+1, Kosta a écrit :
>>
>> Regarding OSX, take a look at ticket 21944 
>>  [basically a way to either 
>> specify where to find the openssl headers or to use the homebrew headers if 
>> available].
>>
>> The homebrew package can be made to depend on the openssl package. 
>> Finally, regarding packaged .app - I don't know. I think it would be 
>> reasonable to prompt the user about this issue if the dynamic library is 
>> not found. I may be wrong, but I think that in recent years homebrew has 
>> become the de-facto package manager and in older OS versions openssl was 
>> present, so it would be fairly reasonable to just prompt the user to 
>> install homebrew and then install via homebrew.
>>
>> Cheers,
>> Kosta
>>
>> -- 
>> Konstantin Kliakhandler
>> http://slumpy.org
>>   )°) )°( (°(
>>
>> On 15 January 2017 at 15:51, Emmanuel Charpentier > > wrote:
>>
>>> A first step  towards a 
>>> solution awaits your comments and review.
>>>
>>> Plan :
>>>
>>>1. Document OpenSSL dependency, mention the possibility of compiling 
>>>againts GnuTLS (with drawbacks)
>>>2. Get OpenSSL development libs on the machines producing Unix 
>>>binary tarballs/packages.
>>>3. (To be discussed) : create a standard "SSL" package serving as a 
>>>backup, allowing compilation on OpenSSL-less machines. As done for git, 
>>>this package should do nothing if OpenSSL is installed systemwide.
>>>4. Complete curl as a standard package, which would allow :
>>>5. Upgrade R. Pffwww...
>>>
>>> Unsolved problem : What about Macs (I don't have a Mac and can't 
>>> contribute).
>>>
>>> To be discussed : Cygwin (advoce from Erik Bray keenly awaited...).
>>>
>>> HTH,
>>>
>>> --
>>> Emmanuel Charpentier
>>>
>>> Le dimanche 1 janvier 2017 02:55:42 UTC+1, Emmanuel Charpentier a écrit :

 Dear list,

 We have three separate, but interacting, difficulties with SSL/TLS 
 support in Sage. I'll summarize the results of the efforts of several 
 people who tracked them, and propose a couple of solutions.

 *I) Python now (discreetly) depends on Open SSL.*

 Their license page  states :

> The modules hashlib 
> , 
> posix , ssl 
> , crypt 
>  use the 
> OpenSSL library for added performance if made available by the 
> operating system. Additionally, the Windows and Mac OS X installers for 
> Python may include a copy of the OpenSSL libraries, so we include a copy 
> of 
> the OpenSSL license here:
>
 followed by the bizarre OpenSSL license. For our purpose, the important 
 statement is *"use the OpenSSL library for added performance if made 
 available by the operating system."*.

 "Added performance, my a^htired foot : Thierry has checked the 
 possibilities of an OpenSSL-less Sage, and I have further checked other 
 possibilities. Our trials conclusively demonstrate that Gnu TLS can't be 
 substituted to OpenSSL for at least the following reasons :

- Sage's pip is non-functionnal when compiled against Gnu TLS
- Ditto for Sage's git
- I understand (but have not checked) that  Python's hashlib 
module, which depends on openssl, is used in Sage.


 However, contrary to my expectations, R 3.3.2 *can* be compiled in 
 Sage against a curl library using Gnu TLS and keep a functional HTTPS 
 access to R repositories.

 Consequences :

- Sage *can*be built and run without OpenSSL support, (as long as R 
is < 3.3 or  some SSL support is available for R >= 3.3), but this 
 system 
will have severe limitations (among others, no access to pip resources, 
questionable  support for Sage's git).
- OpenSSL can be retrofitted in such a system by installing the 
openssl package, but this retrofit becomes effective after 
 recompilation of 
python2 (at least).

 This 

[sage-devel] Re: Current Maxima version

[Dima Pasechnik]

I can confirm that this example also works on Maxima 5.39.0 running on SBCL 
1.3.12.
(I thought for a moment that it's a regression from 5.38.1 to 5.39.0...)

I suspect this could be fixed by an upgrade of ECL to 16.1.3 - something 
that is dealt with on  
#22191 and appears to be tricky.


On Monday, November 28, 2016 at 9:26:19 PM UTC, Paul Masson wrote:
>
> The version of Maxima that ships with Sage is 5.35.1 from December 2014, 
> while the most recent version is 5.38.1 from May 2016.
>
> Is there a compelling reason not to upgrade this package? Surely some of 
> the Maxima bug fixes will be relevant to Sage.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: R fails to compile

[Rob Gross]

It did get built and installed.  I even reinstalled with sage -i -f to make 
sure.

libiconv-1.14 is installed on all of the three Macs that I tried to 
upgrade.  On one system, no problem with the upgrade.  On the other two, R 
failed to compile (though everything else is fine).  Understanding this is 
above my pay grade.--Rob

On Wednesday, January 18, 2017 at 1:32:04 PM UTC-5, Jean-Pierre Flori wrote:
>
> Strange, Sage used to optionally build iconv on retarded systems.
>
> On Wednesday, January 18, 2017 at 2:22:47 PM UTC+1, Emmanuel Charpentier 
> wrote:
>>
>> Forgot to add : ISTR that R has depended on an external iconv for a long 
>> while. I didn't see it would now be mandatory...
>>
>> --
>> Emmanuel Charpentier
>>
>> Le mercredi 18 janvier 2017 14:15:57 UTC+1, Emmanuel Charpentier a écrit :
>>>
>>> Do you have iconv installed systemwide ?
>>>
>>> Le mardi 17 janvier 2017 03:24:54 UTC+1, Rob Gross a écrit :

 Hi,

 I tried to upgrade to 7.5.1 on several different Macs which I thought 
 had identical software.

 However, on one of them, R failed to compile, with the error:

   installing 'sysdata.rda'
 dyld: Symbol not found: __libiconv_version
   Referenced from: 
 /Users/gross/sage-7.0/local/var/tmp/sage/build/r-3.2.4-revised.p0/src/lib/libR.dylib
   Expected in: flat namespace
  in 
 /Users/gross/sage-7.0/local/var/tmp/sage/build/r-3.2.4-revised.p0/src/lib/libR.dylib
 /bin/sh: line 1: 22794 Doneecho 
 "tools:::sysdata2LazyLoadDB(\"./R/sysdata.rda\",\"../../../library/tools/R\")"
  22795 Abort trap: 6   | R_DEFAULT_PACKAGES=NULL LC_ALL=C 
 ../../../bin/R --vanilla --slave

 Any ideas?

 Thanks.--Rob




-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: R fails to compile

[Jean-Pierre Flori]

On Wednesday, January 18, 2017 at 7:36:37 PM UTC+1, Emmanuel Charpentier 
wrote:
>
> It also used to build pcre, an lzma library and SSL tools. No longer since 
> 3.3, which is an itch I tried to scratch for 8 months... Hence also my 
> insistence on the SSL tragicomedy.
>
No I mean Sage itself!
Not through R.
https://github.com/sagemath/sage/tree/master/build/pkgs/iconv

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: is handling of Inf/Infinity/infinity affected by the 1st call to symbolics?

[Peter Luschny]

>
> This is now
> https://trac.sagemath.org/ticket/22201
>

Thanks!

P.S. Do you know that there are functions which work correctly
but advertise to use instead functions which are buggy?
Hint: 22069

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: is handling of Inf/Infinity/infinity affected by the 1st call to symbolics?

[Peter Luschny]

R> Actually the example makes it necessary to completely abandon
R> the original GiNaC series code and use Maxima as fallback in the
R> cases that cannot be handled by the fast rational Pynac series code.

Unfortunately this will not help much. Maxima/taylor is also
unable to compute these functions even for modest values of m
efficiently as you can see from the next example:

def P(m, n):
x, z = var('x, z')
if m == 1: return Integer(1)
w = exp(2 * pi * I / m)
o = sum(exp(z * w^k) for k in range(m)) / m
f = exp(z*x) * (exp(z) / o - 1)
t = f.taylor(z, 0, n+1)
return factorial(n) * t.coefficient(z, n)

for m in [1,2,3,4,5,6,7,11,13]:
print [m], [P(m, n).subs(x=0) for n in (0..10)]

AFAIK there is only one CAS which can handle these things
(which are basic!) efficiently: Mathematica. So if I would
put something on trac it would be an enhancement request:
"Implement the Mittag-Leffler function!".

Peter

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: R fails to compile

[Emmanuel Charpentier]

It also used to build pcre, an lzma library and SSL tools. No longer since
3.3, which is an itch I tried to scratch for 8 months... Hence also my
insistence on the SSL tragicomedy.

--
Emmanuel Charpentier


Le 18 janv. 2017 19:32, "Jean-Pierre Flori"  a écrit :

> Strange, Sage used to optionally build iconv on retarded systems.
>
> On Wednesday, January 18, 2017 at 2:22:47 PM UTC+1, Emmanuel Charpentier
> wrote:
>>
>> Forgot to add : ISTR that R has depended on an external iconv for a long
>> while. I didn't see it would now be mandatory...
>>
>> --
>> Emmanuel Charpentier
>>
>> Le mercredi 18 janvier 2017 14:15:57 UTC+1, Emmanuel Charpentier a écrit :
>>>
>>> Do you have iconv installed systemwide ?
>>>
>>> Le mardi 17 janvier 2017 03:24:54 UTC+1, Rob Gross a écrit :

 Hi,

 I tried to upgrade to 7.5.1 on several different Macs which I thought
 had identical software.

 However, on one of them, R failed to compile, with the error:

   installing 'sysdata.rda'
 dyld: Symbol not found: __libiconv_version
   Referenced from: /Users/gross/sage-7.0/local/va
 r/tmp/sage/build/r-3.2.4-revised.p0/src/lib/libR.dylib
   Expected in: flat namespace
  in /Users/gross/sage-7.0/local/var/tmp/sage/build/r-3.2.4-revis
 ed.p0/src/lib/libR.dylib
 /bin/sh: line 1: 22794 Doneecho
 "tools:::sysdata2LazyLoadDB(\"./R/sysdata.rda\",\"../../../l
 ibrary/tools/R\")"
  22795 Abort trap: 6   | R_DEFAULT_PACKAGES=NULL LC_ALL=C
 ../../../bin/R --vanilla --slave

 Any ideas?

 Thanks.--Rob


 --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/sage-devel/gwHnMT_cTgI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: R fails to compile

[Jean-Pierre Flori]

Strange, Sage used to optionally build iconv on retarded systems.

On Wednesday, January 18, 2017 at 2:22:47 PM UTC+1, Emmanuel Charpentier 
wrote:
>
> Forgot to add : ISTR that R has depended on an external iconv for a long 
> while. I didn't see it would now be mandatory...
>
> --
> Emmanuel Charpentier
>
> Le mercredi 18 janvier 2017 14:15:57 UTC+1, Emmanuel Charpentier a écrit :
>>
>> Do you have iconv installed systemwide ?
>>
>> Le mardi 17 janvier 2017 03:24:54 UTC+1, Rob Gross a écrit :
>>>
>>> Hi,
>>>
>>> I tried to upgrade to 7.5.1 on several different Macs which I thought 
>>> had identical software.
>>>
>>> However, on one of them, R failed to compile, with the error:
>>>
>>>   installing 'sysdata.rda'
>>> dyld: Symbol not found: __libiconv_version
>>>   Referenced from: 
>>> /Users/gross/sage-7.0/local/var/tmp/sage/build/r-3.2.4-revised.p0/src/lib/libR.dylib
>>>   Expected in: flat namespace
>>>  in 
>>> /Users/gross/sage-7.0/local/var/tmp/sage/build/r-3.2.4-revised.p0/src/lib/libR.dylib
>>> /bin/sh: line 1: 22794 Doneecho 
>>> "tools:::sysdata2LazyLoadDB(\"./R/sysdata.rda\",\"../../../library/tools/R\")"
>>>  22795 Abort trap: 6   | R_DEFAULT_PACKAGES=NULL LC_ALL=C 
>>> ../../../bin/R --vanilla --slave
>>>
>>> Any ideas?
>>>
>>> Thanks.--Rob
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Current Maxima version

[Dima Pasechnik]

On Wednesday, January 18, 2017 at 2:43:05 PM UTC, Emmanuel Charpentier 
wrote:
>
> Nice ! Thank you very much.
>
> However, I see that one of my pet peeves, now solved in Maxima, isn't yet 
> solved in Maxima-from-Sage :
>
> /* Maxima, as packaged in Debian */
>
> charpent@SAP5057241:~$ maxima
>
> Maxima 5.38.1 http://maxima.sourceforge.net
> using Lisp GNU Common Lisp (GCL) GCL 2.6.12
> Distributed under the GNU Public License. See the file COPYING.
> Dedicated to the memory of William Schelter.
> The function bug_report() provides bug reporting information.
> (%i1) display2d:false;
>
> (%o1) false
> (%i2) integrate(f(x),x);
>
> (%o2) 'integrate(f(x),x)
> (%i3) taylor(integrate(f(x),x),x,x_0,2);
>
> (%o3) 'at('integrate(f(x),x),x = x_0)+f(x_0)*(x-x_0)
>  +(('at('diff(f(x),x,1),x = x_0))
>   *(x-x_0)^2)
>   /2
>
> /* Sage's Maxima */
>
> charpent@SAP5057241:~$ sage -maxima
> ;;; Loading #P"/usr/local/sage-7/local/lib/ecl/sb-bsd-sockets.fas"
> ;;; Loading #P"/usr/local/sage-7/local/lib/ecl/sockets.fas"
> ;;; Loading #P"/usr/local/sage-7/local/lib/ecl/defsystem.fas"
> ;;; Loading #P"/usr/local/sage-7/local/lib/ecl/cmp.fas"
> Maxima 5.39.0 http://maxima.sourceforge.net
> using Lisp ECL 16.1.2
> Distributed under the GNU Public License. See the file COPYING.
> Dedicated to the memory of William Schelter.
> The function bug_report() provides bug reporting information.
> (%i1) display2d:false;
>
> (%o1) false
> (%i2) integrate(f(x),x);  
>
> (%o2) 'integrate(f(x),x)
> (%i3) taylor(integrate(f(x),x),x,x_0,2);
>
> taylor: unable to expand at a point specified in:
> 'integrate(f(x),x)
>  -- an error. To debug this try: debugmode(true);
>
> This is a bit annoying : the ability to manipulate such expression is 
> useful...
>
> Does this deserve a ticket ? I don't see it in our current list 
> .
>

perhaps an issue on Maxima bug tracker is more appropriate here? 

>
> HTH,
>
> --
> Emmanuel Charpentier
>
>
> Le mercredi 18 janvier 2017 13:31:21 UTC+1, Dima Pasechnik a écrit :
>>
>> ticket upgrading Maxima tp 5.39.0 is ready for review now: 
>> https://trac.sagemath.org/ticket/18920
>>
>> On Monday, November 28, 2016 at 9:26:19 PM UTC, Paul Masson wrote:
>>>
>>> The version of Maxima that ships with Sage is 5.35.1 from December 2014, 
>>> while the most recent version is 5.38.1 from May 2016.
>>>
>>> Is there a compelling reason not to upgrade this package? Surely some of 
>>> the Maxima bug fixes will be relevant to Sage.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: is handling of Inf/Infinity/infinity affected by the 1st call to symbolics?

[Ralf Stephan]

On Wednesday, January 18, 2017 at 4:55:03 PM UTC+1, Ralf Stephan wrote:
>
> Actually the example makes it necessary to completely abandon
> the original GiNaC series code and use Maxima as fallback in the
> cases that cannot be handled by the fast rational Pynac series code.
>

This is now
https://trac.sagemath.org/ticket/22201 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: is handling of Inf/Infinity/infinity affected by the 1st call to symbolics?

[Ralf Stephan]

Actually the example makes it necessary to completely abandon
the original GiNaC series code and use Maxima as fallback in the
cases that cannot be handled by the fast rational Pynac series code.

Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: is handling of Inf/Infinity/infinity affected by the 1st call to symbolics?

[Ralf Stephan]

On Wednesday, January 18, 2017 at 3:22:20 PM UTC+1, Peter Luschny wrote:
>
> I cannot reproduce your claim, in the contrary.
>

You are quite right. Your example is not accelerated by the recent
improvements. So I should have said way faster in many cases.

Regards,

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Current Maxima version

[Emmanuel Charpentier]

Nice ! Thank you very much.

However, I see that one of my pet peeves, now solved in Maxima, isn't yet 
solved in Maxima-from-Sage :

/* Maxima, as packaged in Debian */

charpent@SAP5057241:~$ maxima

Maxima 5.38.1 http://maxima.sourceforge.net
using Lisp GNU Common Lisp (GCL) GCL 2.6.12
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
The function bug_report() provides bug reporting information.
(%i1) display2d:false;

(%o1) false
(%i2) integrate(f(x),x);

(%o2) 'integrate(f(x),x)
(%i3) taylor(integrate(f(x),x),x,x_0,2);

(%o3) 'at('integrate(f(x),x),x = x_0)+f(x_0)*(x-x_0)
 +(('at('diff(f(x),x,1),x = x_0))
  *(x-x_0)^2)
  /2

/* Sage's Maxima */

charpent@SAP5057241:~$ sage -maxima
;;; Loading #P"/usr/local/sage-7/local/lib/ecl/sb-bsd-sockets.fas"
;;; Loading #P"/usr/local/sage-7/local/lib/ecl/sockets.fas"
;;; Loading #P"/usr/local/sage-7/local/lib/ecl/defsystem.fas"
;;; Loading #P"/usr/local/sage-7/local/lib/ecl/cmp.fas"
Maxima 5.39.0 http://maxima.sourceforge.net
using Lisp ECL 16.1.2
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
The function bug_report() provides bug reporting information.
(%i1) display2d:false;

(%o1) false
(%i2) integrate(f(x),x);  

(%o2) 'integrate(f(x),x)
(%i3) taylor(integrate(f(x),x),x,x_0,2);

taylor: unable to expand at a point specified in:
'integrate(f(x),x)
 -- an error. To debug this try: debugmode(true);

This is a bit annoying : the ability to manipulate such expression is 
useful...

Does this deserve a ticket ? I don't see it in our current list 
.

HTH,

--
Emmanuel Charpentier


Le mercredi 18 janvier 2017 13:31:21 UTC+1, Dima Pasechnik a écrit :
>
> ticket upgrading Maxima tp 5.39.0 is ready for review now: 
> https://trac.sagemath.org/ticket/18920
>
> On Monday, November 28, 2016 at 9:26:19 PM UTC, Paul Masson wrote:
>>
>> The version of Maxima that ships with Sage is 5.35.1 from December 2014, 
>> while the most recent version is 5.38.1 from May 2016.
>>
>> Is there a compelling reason not to upgrade this package? Surely some of 
>> the Maxima bug fixes will be relevant to Sage.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: is handling of Inf/Infinity/infinity affected by the 1st call to symbolics?

[Peter Luschny]

Hi Ralf!

R> there is no need for taylor() (Maxima)
R> if you use series() (Pynac) which is way faster.

I cannot reproduce your claim, in the contrary.
Please consider this simple example:

def num(m, n, ser):
z = var('z')
w = exp(2 * pi * I / m)
o = sum(exp(z * w^k) for k in range(m)) / m
f = 1 / o
if ser:
t = f.series(z, n + 1)
else:
t = taylor(f, z, 0, n + 1)
return factorial(n) * t.coefficient(z, n) 

ser = lambda m,n: sum(binomial(m*n,m*k)*num(m,m*k,true )*k/n for k in 
(1..n))
tay = lambda m,n: sum(binomial(m*n,m*k)*num(m,m*k,false)*k/n for k in 
(1..n))

---

import time
print time.clock()
print [[tay(m,n) for n in (1..6)] for m in (1..5)]
print time.clock()
print [[ser(m,n) for n in (1..6)] for m in (1..5)]
print time.clock()

In fact if I would not have killed the program I think 
the series version would still run. 
If I have misunderstood, please do enlighten me. 

Peter

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: R fails to compile

[Emmanuel Charpentier]

Forgot to add : ISTR that R has depended on an external iconv for a long 
while. I didn't see it would now be mandatory...

--
Emmanuel Charpentier

Le mercredi 18 janvier 2017 14:15:57 UTC+1, Emmanuel Charpentier a écrit :
>
> Do you have iconv installed systemwide ?
>
> Le mardi 17 janvier 2017 03:24:54 UTC+1, Rob Gross a écrit :
>>
>> Hi,
>>
>> I tried to upgrade to 7.5.1 on several different Macs which I thought had 
>> identical software.
>>
>> However, on one of them, R failed to compile, with the error:
>>
>>   installing 'sysdata.rda'
>> dyld: Symbol not found: __libiconv_version
>>   Referenced from: 
>> /Users/gross/sage-7.0/local/var/tmp/sage/build/r-3.2.4-revised.p0/src/lib/libR.dylib
>>   Expected in: flat namespace
>>  in 
>> /Users/gross/sage-7.0/local/var/tmp/sage/build/r-3.2.4-revised.p0/src/lib/libR.dylib
>> /bin/sh: line 1: 22794 Doneecho 
>> "tools:::sysdata2LazyLoadDB(\"./R/sysdata.rda\",\"../../../library/tools/R\")"
>>  22795 Abort trap: 6   | R_DEFAULT_PACKAGES=NULL LC_ALL=C 
>> ../../../bin/R --vanilla --slave
>>
>> Any ideas?
>>
>> Thanks.--Rob
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Our SSL serial drama-cum-cliffhanger

[Emmanuel Charpentier]

I'm not sure to understand the ticket. Does that means that OS X Sage will 
depend on Apple's SSL library ? Or depend on a systemwide OpenSSL ? Or am I 
mistaken entirely ?

--
Emmanuel Charpentier

Le lundi 16 janvier 2017 21:07:40 UTC+1, Kosta a écrit :
>
> Regarding OSX, take a look at ticket 21944 
>  [basically a way to either 
> specify where to find the openssl headers or to use the homebrew headers if 
> available].
>
> The homebrew package can be made to depend on the openssl package. 
> Finally, regarding packaged .app - I don't know. I think it would be 
> reasonable to prompt the user about this issue if the dynamic library is 
> not found. I may be wrong, but I think that in recent years homebrew has 
> become the de-facto package manager and in older OS versions openssl was 
> present, so it would be fairly reasonable to just prompt the user to 
> install homebrew and then install via homebrew.
>
> Cheers,
> Kosta
>
> -- 
> Konstantin Kliakhandler
> http://slumpy.org
>   )°) )°( (°(
>
> On 15 January 2017 at 15:51, Emmanuel Charpentier  > wrote:
>
>> A first step  towards a solution 
>> awaits your comments and review.
>>
>> Plan :
>>
>>1. Document OpenSSL dependency, mention the possibility of compiling 
>>againts GnuTLS (with drawbacks)
>>2. Get OpenSSL development libs on the machines producing Unix binary 
>>tarballs/packages.
>>3. (To be discussed) : create a standard "SSL" package serving as a 
>>backup, allowing compilation on OpenSSL-less machines. As done for git, 
>>this package should do nothing if OpenSSL is installed systemwide.
>>4. Complete curl as a standard package, which would allow :
>>5. Upgrade R. Pffwww...
>>
>> Unsolved problem : What about Macs (I don't have a Mac and can't 
>> contribute).
>>
>> To be discussed : Cygwin (advoce from Erik Bray keenly awaited...).
>>
>> HTH,
>>
>> --
>> Emmanuel Charpentier
>>
>> Le dimanche 1 janvier 2017 02:55:42 UTC+1, Emmanuel Charpentier a écrit :
>>>
>>> Dear list,
>>>
>>> We have three separate, but interacting, difficulties with SSL/TLS 
>>> support in Sage. I'll summarize the results of the efforts of several 
>>> people who tracked them, and propose a couple of solutions.
>>>
>>> *I) Python now (discreetly) depends on Open SSL.*
>>>
>>> Their license page  states :
>>>
 The modules hashlib 
 , 
 posix , ssl 
 , crypt 
  use the 
 OpenSSL library for added performance if made available by the 
 operating system. Additionally, the Windows and Mac OS X installers for 
 Python may include a copy of the OpenSSL libraries, so we include a copy 
 of 
 the OpenSSL license here:

>>> followed by the bizarre OpenSSL license. For our purpose, the important 
>>> statement is *"use the OpenSSL library for added performance if made 
>>> available by the operating system."*.
>>>
>>> "Added performance, my a^htired foot : Thierry has checked the 
>>> possibilities of an OpenSSL-less Sage, and I have further checked other 
>>> possibilities. Our trials conclusively demonstrate that Gnu TLS can't be 
>>> substituted to OpenSSL for at least the following reasons :
>>>
>>>- Sage's pip is non-functionnal when compiled against Gnu TLS
>>>- Ditto for Sage's git
>>>- I understand (but have not checked) that  Python's hashlib module, 
>>>which depends on openssl, is used in Sage.
>>>
>>>
>>> However, contrary to my expectations, R 3.3.2 *can* be compiled in Sage 
>>> against a curl library using Gnu TLS and keep a functional HTTPS access to 
>>> R repositories.
>>>
>>> Consequences :
>>>
>>>- Sage *can*be built and run without OpenSSL support, (as long as R 
>>>is < 3.3 or  some SSL support is available for R >= 3.3), but this 
>>> system 
>>>will have severe limitations (among others, no access to pip resources, 
>>>questionable  support for Sage's git).
>>>- OpenSSL can be retrofitted in such a system by installing the 
>>>openssl package, but this retrofit becomes effective after recompilation 
>>> of 
>>>python2 (at least).
>>>
>>> This latter "solution" is, at best, a contraption (even if something in 
>>> this direction has been proposed 
>>>  
>>> back in 2012 to solve the very same problem). Therefore :
>>>
>>>- we *must at minimum* advertise this problem in the REAME.md file 
>>>and recommend checking the presence of OpenSSL, and recommend the 
>>>installation of openssl development files for Sage compilation. In this 
>>>case, we would 

[sage-devel] Re: R fails to compile

[Emmanuel Charpentier]

Do you have iconv installed systemwide ?

Le mardi 17 janvier 2017 03:24:54 UTC+1, Rob Gross a écrit :
>
> Hi,
>
> I tried to upgrade to 7.5.1 on several different Macs which I thought had 
> identical software.
>
> However, on one of them, R failed to compile, with the error:
>
>   installing 'sysdata.rda'
> dyld: Symbol not found: __libiconv_version
>   Referenced from: 
> /Users/gross/sage-7.0/local/var/tmp/sage/build/r-3.2.4-revised.p0/src/lib/libR.dylib
>   Expected in: flat namespace
>  in 
> /Users/gross/sage-7.0/local/var/tmp/sage/build/r-3.2.4-revised.p0/src/lib/libR.dylib
> /bin/sh: line 1: 22794 Doneecho 
> "tools:::sysdata2LazyLoadDB(\"./R/sysdata.rda\",\"../../../library/tools/R\")"
>  22795 Abort trap: 6   | R_DEFAULT_PACKAGES=NULL LC_ALL=C 
> ../../../bin/R --vanilla --slave
>
> Any ideas?
>
> Thanks.--Rob
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Current Maxima version

[Dima Pasechnik]

ticket upgrading Maxima tp 5.39.0 is ready for review 
now: https://trac.sagemath.org/ticket/18920

On Monday, November 28, 2016 at 9:26:19 PM UTC, Paul Masson wrote:
>
> The version of Maxima that ships with Sage is 5.35.1 from December 2014, 
> while the most recent version is 5.38.1 from May 2016.
>
> Is there a compelling reason not to upgrade this package? Surely some of 
> the Maxima bug fixes will be relevant to Sage.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Can't run binaries

[Sarfo]

On Wednesday, 18 January 2017 08:57:57 UTC, Eric Gourgoulhon wrote:
>
> Le mercredi 18 janvier 2017 09:41:38 UTC+1, Dima Pasechnik a écrit :
>>
>> compiling from source might be easier and faster than trying a binary 
>> that is not quite matching the OS.
>>
>>
> Yes indeed. Here are a few hints to build from source: 
>
> Thank you very much Eric
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Can't run binaries

[Eric Gourgoulhon]

Le mercredi 18 janvier 2017 09:41:38 UTC+1, Dima Pasechnik a écrit :
>
> compiling from source might be easier and faster than trying a binary that 
> is not quite matching the OS.
>
>
Yes indeed. Here are a few hints to build from source: 

1/ Make sure that the prerequisites are installed on your system, cf. 
http://doc.sagemath.org/html/en/installation/source.html#prerequisites
For Ubuntu 16.04 the list of packages to install is
https://wiki.sagemath.org/prerequisitesUbuntu
I guess it is should be pretty similar for Linux Mint 18

2/ run the following commands in a terminal:
git clone https://github.com/sagemath/sage.git
cd sage  
MAKE="make -j8" make 
You may adapt the 8 in "-j8" to the number of threads you want 
to use for the parallel build, depending on your CPU. 

Best wishes,

Eric. 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Can't run binaries

[Sarfo]

Thank you all for the responses

I have reinstall the OS and everything works fine now.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Can't run binaries

[Dima Pasechnik]

compiling from source might be easier and faster than trying a binary that 
is not quite matching the OS.


On Tuesday, January 17, 2017 at 5:02:39 PM UTC, Sarfo wrote:
>
>
>
> Thanks Eric
>
> I have download the latest binaries but I still get the same error
>
> My OS is : Linux Mint 18 Cinnamon 64-bit
> Cinnamon Version: 3.0.6
> Linux Kernel 4.4.0-21-generic
>
>
> gyamfy@holiness ~/SageMath $ ./sage
> RecursionError: maximum recursion depth exceeded during compilation
> ┌┐
> │ SageMath version 7.5.1, Release Date: 2017-01-15   │
> │ Type "notebook()" for the browser-based notebook interface.│
> │ Type "help()" for help.│
> └┘
>
> ERROR:  The Sage installation tree has moved
>
> from 
> /home/buildbot/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidmas391yaj2
>   to /home/gyamfy/SageMath
>
> This is not supported, and Sage will not work. To install Sage from a
> binary package:
>
> 1. Open the .tar.bz2 archive (or .dmg on OSX)
>
> 2. Move the SageMath folder/app to where you want it to be. You can
>also rename the directory now.
>
> 3. Start sage for the first time. This will then automatically patch
>paths in binaries.
>
> After starting Sage for the first time you cannot change the
> installation any more. To install Sage elsewhere, start over from the
> binary package. Or recompile Sage from scratch in the new location
> ("make distclean && make")
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.