Let me point out that this is most probably discussed on https://trac.sagemath.org/ticket/26899
On Thu, Mar 7, 2019 at 12:35 PM E. Madison Bray <[email protected]> wrote: > > On Thu, Mar 7, 2019 at 12:26 PM Dima Pasechnik <[email protected]> wrote: > > > > On Thu, Mar 7, 2019 at 10:54 AM Andrew <[email protected]> wrote: > > > > > > Although I have not had this problem myself, zlib seems to be an issue > > > for some macs. For zlib, John H Palmieri recommends: > > > > > > ./sage -f zlib python2 python3 && make > > > > this gets me thinking whether https://trac.sagemath.org/ticket/26286 > > is to blame, specifically the part that is able to pick up the system's > > zlib. > > > > Note that ./sage -f zlib will install the Sage's copy of zlib regardless, > > and > > somehow zlib from the system might pass our checks, but be rejected by > > python > > (in which case this is probably a python bug) > > > > Is this really the case here? > > > > > > > > Presumably, you have already installed the system headers using something > > > like: > > > > > > open > > > /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg > > > > > > > > > > > > > > > On Thursday, 7 March 2019 20:24:17 UTC+11, Vincent Klein wrote: > > >> > > >> Ok. Thank you for your answer. > > In the spkg-build [1] for python2/3, there is a section toward the end > which checks whether or not several required extension modules built > successfully. This is necessary, because the Python build system > itself does not error out if some extension module fails to build > (from the Python perspective most of these extension modules are > technically optional, and it just builds as many of them as it can). > > Currently it only checks: > > * ctypes > * math > * hashlib > * crypt > * readline > * socket > > And on MacOS it also checks for a module called "_scproxy". I have no > idea what that is or why it's only on MacOS. > > Since I think several people have had trouble with zlib on MacOS, > especially since 10.14, we should probably add "zlib" to the above > list, as it's certainly necessary for the Python "zlib" module to be > available. I would suggest we also go ahead and add "ssl" as well. I > don't think there's any reason anymore to not build Python with SSL > support, and may people do so anyways without realizing it and then > complain when they can't `pip install` anything. > > Perhaps as a middle ground the spkg-build could take an optional > environment variable to *not* require SSL, but I would require it by > default... > > - > > [1] > https://gitlab.com/sagemath/sage/blob/master/build/pkgs/python3/spkg-build#L108 > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
