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

surely people would not mind a HB based way to build Sage. Long ago HB was a pain,due to linking to wrong libs all the time. Since then Sage switch to using rpath, and it is much more robust in this sense. -- You received this message because you are subscribed to the Google Groups

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

P.S. I looked at the ticket now. I don't know exactly what was wrong on their end, but I have homebrew gcc (6.3.0) installed, including gfortran, and it did not break my build, as far as I can tell (at the very least, it was successfully built and runs fine the simple stuff I usually use it for).

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

That may be true, but IMHO this is already a specific issue of incompatibility with a specific package, rather than a systemic incompatibility with HB itself (e.g. as would be the case if HB relied on said version of gfortran). I see it as no different than a situation where the user installed

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

It depend what compilers are exposed. Last time someone filled a bug, gfortran from brew was interfering with the gfortran sage installs. https://trac.sagemath.org/ticket/22112 Francois On 25/01/17 11:46, Konstantin Kliakhandler wrote: Ah, I misunderstood the question. AFAICT homebrew does not

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

Ah, I misunderstood the question. AFAICT homebrew does not adversely affect the sage built. In particular, I was able to successfully build it several times with 7.5.betaX 7.5.rcX and 7.5, on two separate machines (on which I also have HB installed). -- Konstantin Kliakhandler

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

The question is, if you have homebrew installed, can you build Sage from source? That is, extract the source tarball, type 'make' in the sage directory, and have it complete successfully. I think the motivation behind the question is, in the past, the presence of fink or macports prevented

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

I'm not sure exactly what you mean; I am able to *install* sage via homebrew - what it does is effectively download the .dmg archive and unpack it in an appropriate location. There is no homebrew package for building sage from source, however. I can (probably) make one if necessary, however. On

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

Are you able to build Sage under/in homebrew? On Thursday, January 19, 2017 at 3:01:49 PM UTC, Kosta wrote: > > Right now (pre-ticket) if you try to build sage on OSX Sierra and above, > it will be built without > OpenSSL support. I'm not sure what happens if you download a prebuilt > package

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

Right now (pre-ticket) if you try to build sage on OSX Sierra and above, it will be built without OpenSSL support. I'm not sure what happens if you download a prebuilt package but somehow I assumed that if you don't have OpenSSL installed, then you can't use OpenSSL (otherwise I don't understand

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

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

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

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

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

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

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

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

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

I know that in linux, one approach that is sometimes taken is having the software download the components "dirty" components separately (e.g. some proprietary drivers and firmware, as well as fonts and codecs). Might it be possible to take a similar approach? Best, Kosta On Sunday, 1 January

[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