Changes between Version 3 and Version 4 of Ticket #30556


Ignore:
Timestamp:
09/11/20 19:23:22 (15 months ago)
Author:
slelievre
Comment:

Even when configuring with --enable-openssl, I think openssl may be built after python3.

So currently one really has to separate into two steps:

$ make openssl
$ make

or later have to repair with

$ sage -i openssl
$ sage -f python3

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #30556 – Description

    v3 v4  
    1 When building Python 3.8.5, Sage does not build its
    2 ssl module even if OpenSSL is available system-wide.
     1Building Sage with its own Python 3 can easily produce
     2a Python 3 missing its `_ssl` module.
    33
    4 This differs from what happened with Python 3.7.
     4Python's `_ssl` module is only built if OpenSSL (with headers)
     5is available, either via the system or via the `openssl` spkg.
    56
    6 Reported on sage-release:
     7The result is reduced functionality:
    78
    8 - [https://groups.google.com/d/msg/sage-release/hobZzw74Rv0/pkiQFTg9AQAJ initial report on sage-release]
     9- it hinders installing pip packages
     10- it hinders working with Jupyter
     11
    912
    1013See also:
    1114
     15- many reports on Ask Sage and sage-support
     16- [https://groups.google.com/d/msg/sage-release/hobZzw74Rv0/pkiQFTg9AQAJ sage-release: cannot start Jupyter due to missing _ssl module]
    1217- #30557: Add spkg-configure.m4 for openssl
    1318- #29555: Upgrade: OpenSSL 3.0, make it a standard package