Changes between Version 1 and Version 8 of Ticket #22756


Ignore:
Timestamp:
04/05/17 21:43:47 (3 years ago)
Author:
jhpalmieri
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #22756

    • Property Commit changed from to c050438fa802d56738cc7084254579c5610b7358
    • Property Branch changed from to u/jhpalmieri/python3_osx
  • Ticket #22756 – Description

    v1 v8  
    33Examples (all start with `make distclean`):
    44
    5 - `./sage -i python3`. Then `python3` works, but the `_scproxy` and `_lzma` modules fail to build. The error for `_lzma` is
     5- `./sage -i python3`. Then `python3` works, but the `_scproxy` (on OS X 10.12) and `_lzma` modules fail to build. We've seen the `_scproxy` error before: the solution is to compile with clang, at least on recent versions of OS X. The error for `_lzma` is
    66{{{
    77/Users/palmieri/Desktop/Sage_stuff/sage_builds/TESTING/sage-8.0.beta0/local/var/tmp/sage/build/python3-3.5.1/src/Modules/_lzmamodule.c:19:18: fatal error: lzma.h: No such file or directory
     
    2727- if we build Python3 with `clang` but we build Python2 first, then we get the same error as above.
    2828
    29 So I propose that we build Python3 with `clang` and we make `xz` a dependency. I don't know why the Python2 and Python3 builds interfere with each other. We could make `python3` a dependency of `python2`, to force `python3` to be built first, but that feels like treating the symptom, not the problem.
     29So I propose that we build Python3 with `clang` as we already do with Python2, and we make `xz` a dependency. I don't know why the Python2 and Python3 builds interfere with each other. We could make `python3` a dependency of `python2`, to force `python3` to be built first, but that feels like treating the symptom, not the problem.