On Monday, November 21, 2016 at 7:10:49 PM UTC, Emmanuel Charpentier wrote: > > Le lundi 21 novembre 2016 à 10:17 -0800, Volker Braun a écrit : > > Actually OSX is foobar'ed even then, Apple's ancient openssl just doesn't > support TLSv1.2. Some sites are already requiring that: > > osx:~ vbraun$ openssl s_client -connect www.kernel.org:443 > CONNECTED(00000003) > write:errno=54 > > > > Mmm According to https://www.openssl.org/, OpenSSL latest version is > 1.1.0c (dated Noc 10, 2016), which, according to > http://mac.softpedia.com/get/Security/OpenSSL.shtml > <http://www.google.com/url?q=http%3A%2F%2Fmac.softpedia.com%2Fget%2FSecurity%2FOpenSSL.shtml&sa=D&sntz=1&usg=AFQjCNFGXuQNlMSJftXzEAvvsCR1PlEjyQ>, > > compiles on a Mac. > > Does this compilation present special difficulties ? >
in fact, it seems to work; last time I tried it at sage -sh prompt, with Sage's gcc, and it didn't do what I needed. I'm trying the whole binary-pkg thing now, with openssl built by Xcode and installed in /usr/local (not sure whether the build has used extra things I have installed, like extra Perl packages--- yes, OpenSSL 1.1.* has its own, Perl-based, configure system...) Anyhow, I'm stuck at the same place - that git cannot be built, see https://github.com/sagemath/binary-pkg/issues/8 > -- > Emmanuel Charpentier > > Dear list, > > The fact that we can't ship openSSL (see uncountable theads in sage-devel > and others) seems to pose more and more difficulties. See for example this > thread <https://groups.google.com/forum/#!topic/sage-support/rDV9uGT2ViM> > on sage-support, and especially Dima's answer > <https://groups.google.com/d/msg/sage-support/rDV9uGT2ViM/GuKDbhSKAwAJ>, > as well as this annoying ticket <https://trac.sagemath.org/ticket/21767>, > discussed in this saga > <https://groups.google.com/forum/#!topic/sage-devel/QaBdHSNJuKg> . > > Could'nt we add OpenSSL as a prerequisite to Sage, and it"s development > files as a prerequisite to building Sage ? This would require of the user > to install OpenSSL systemwide, thus making it "system software" and > satisfying the strange licensing requirements that bother us. > > One could even do that indirectly, by requiring a systemwide libcurl > supporting https : this would de facto enforce the systemwide installation > of OpenSSL (or a reasonable facsimile). That's what I was trying to do in > this > proposal <https://trac.sagemath.org/ticket/21767#comment:41>... (IIRC, > the problem with libcurl is also bound to OpenSSL : libcurl itself is not a > problem. But I'll have to check : if this is true, we can require OpenSSL > and ship libcurl which will then compile cleanly). > > Comments ? Especially wrt Macs, which seem to be further encumbered by > Apple's dirty tricks... > > Should we have a vote ? > > -- > Emmanuel Charpentier > > > -- > 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/92OdoUbBDbE/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > sage-devel+...@googlegroups.com <javascript:>. > To post to this group, send email to sage-...@googlegroups.com > <javascript:>. > 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.
