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

My 2 cents, not that I know too much about this, would be to openly make it a listed dependency. I don't know how difficult it would be to maintain this as an optional dependency, but it is something we could either abort or warn the user (with a prompt) should they try installing Sage without

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

On Sat, Dec 31, 2016 at 5:55 PM, Emmanuel Charpentier wrote: > Should we openly depend on OpenSSL ? If so, how to express it ? > > I'd vote for that, and for warning of the penalties involved by the non-use > of OpenSSL, probably in terms close to those of the Python license. Just to add to what

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

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

Re: [sage-devel] sage -b fails on SageMathCloud

Hi William, Yes, I was trying to get some older code to run. Removing that line fixes the build problem. So GMP is now available without additional includes? That's great! Thanks, -Jon On Saturday, December 31, 2016 at 1:09:41 PM UTC-5, William wrote: > > The error you get is > >Inte

Re: [sage-devel] sage -b fails on SageMathCloud

The error you get is Internal compiler error: '../ext/gmp.pxi' not found There is no gmp.pxi in your tree: ~/SAGE_INSTALL__2016-12-21/sage-7.4$ find . |grep gmp.pxi ~/SAGE_INSTALL__2016-12-21/sage-7.4$ In fact gmp.pxi was removed from sage years ago, evidently: https://trac.sagemath.org/tic

[sage-devel] sage -b fails on SageMathCloud

Hi, I'm trying to rebuild sage with the 'sage -b' command as described here and get the error below. Are there some additional shell variables that need to be set for this to work? I'm using sage 7.4 build from source on SageM