Le samedi 03 décembre 2016 à 13:02 +0100, Thierry a écrit : > Hi, > > On Sat, Dec 03, 2016 at 10:48:18AM +0100, Emmanuel Charpentier wrote: > [...] > > If you still have this VM, could you try to add the current > > "openssl" > > Sage package and tell us if , after this addition, "sage -pip list" > > works ? > > I droped it, but i can create a new one. Do you mean just add `./sage > -i > openssl` after compiling ? That's what I thought. But you gave me (below) another idea. See below
> Otherwise, give me the exact order of the > operations you want to test (starting from initial deps and make > command). > > I am pretty sure openssl will not be taken into account until you > recompile python2 (at least it was the case a few months ago), python > seems not trying to guess system's libs at runtime. Ok. So we might try the following sequence : 1) in a pristine, openssl-virgin VM, compile Sage, and test pip's ability to work (test 0, negative, as you proved). 2) install Sage's openssl, test pip's ability (test 1) If test1 positive, we win. If test 1 is negative, as you think 3a) update Python (./sage -f python2), and re-test pip's ability (test 2) if test 2 positive, we win (serendipitously). if test2 negative, you just proved that the openssl package is not sufficient. Which answers the "dependency on OpenSSL" question. It would be useful to keep this VM around, because the same tests will be interesting to run in order to test R's ability to use https-only R repositories. HTH, -- Emmanuel Charpentier > > Ciao, > Thierry > -- 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.
