Changes between Version 1 and Version 2 of Ticket #22999, comment 87


Ignore:
Timestamp:
06/02/17 06:52:58 (4 years ago)
Author:
slabbe
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #22999, comment 87

    v1 v2  
    1 > What about
    2 > - keeping the sed of the gcc `spkg-install` patching the `local/include/dispatch/object.h`
    31
    4 On osx 10.10, with 8.0.beta9, I get problem building python2-2.7.13.p1 with errors in the log related to the fact that I moved `local/include/dispatch/object.h` to `local/include/dispatch/object.h.no`. Therefore, it seems that "the sed of the gcc `spkg-install` patching the `local/include/dispatch/object.h`" is necessary.
    52
    6 {{{
    7 [python2-2.7.13.p1] Python build finished, but the necessary bits to build these modules were not found:
    8 [python2-2.7.13.p1] bsddb185           dl                 gdbm           
    9 [python2-2.7.13.p1] imageop            linuxaudiodev      ossaudiodev   
    10 [python2-2.7.13.p1] spwd               sunaudiodev                       
    11 [python2-2.7.13.p1] To find the necessary bits, look in setup.py in detect_modules() for the module's name.
    12 [python2-2.7.13.p1]
    13 [python2-2.7.13.p1]
    14 [python2-2.7.13.p1] Failed to build these modules:
    15 [python2-2.7.13.p1] _scproxy                                             
    16 [python2-2.7.13.p1]
    17 [python2-2.7.13.p1] running build_scripts
    18 [python2-2.7.13.p1] creating build/scripts-2.7
    19 [python2-2.7.13.p1] copying and adjusting /Users/slabbe/Applications/sage-git/local/var/tmp/sage/build/python2-2.7.13.p1/src/Tools/scripts/pydoc -> build/scripts-2.7
    20 [python2-2.7.13.p1] copying and adjusting /Users/slabbe/Applications/sage-git/local/var/tmp/sage/build/python2-2.7.13.p1/src/Tools/scripts/idle -> build/scripts-2.7
    21 [python2-2.7.13.p1] copying and adjusting /Users/slabbe/Applications/sage-git/local/var/tmp/sage/build/python2-2.7.13.p1/src/Tools/scripts/2to3 -> build/scripts-2.7
    22 [python2-2.7.13.p1] copying and adjusting /Users/slabbe/Applications/sage-git/local/var/tmp/sage/build/python2-2.7.13.p1/src/Lib/smtpd.py -> build/scripts-2.7
    23 [python2-2.7.13.p1] changing mode of build/scripts-2.7/pydoc from 644 to 755
    24 [python2-2.7.13.p1] changing mode of build/scripts-2.7/idle from 644 to 755
    25 [python2-2.7.13.p1] changing mode of build/scripts-2.7/2to3 from 644 to 755
    26 [python2-2.7.13.p1] changing mode of build/scripts-2.7/smtpd.py from 644 to 755
    27 [python2-2.7.13.p1] /usr/bin/install -c -m 644 ./Tools/gdb/libpython.py python.exe-gdb.py
    28 [python2-2.7.13.p1] Error: the _scproxy module failed to build.
    29 [python2-2.7.13.p1]
    30 [python2-2.7.13.p1] real    1m2.132s
    31 [python2-2.7.13.p1] user    0m25.040s
    32 [python2-2.7.13.p1] sys    0m28.191s
    33 [python2-2.7.13.p1] ************************************************************************
    34 [python2-2.7.13.p1] Error installing package python2-2.7.13.p1
    35 [python2-2.7.13.p1] ************************************************************************
    36 [python2-2.7.13.p1] Please email sage-devel (http://groups.google.com/group/sage-devel)
    37 }}}
     3What about
     4
     5 - keeping the sed of the gcc spkg-install patching the local/include/dispatch/object.h
     6 - keeping the osx 10.10 patch for cmake-3.8.1
     7 - keeping C=clang and CXX=clang++ for cmake spkg-install and spkg-check
     8 - (maybe) change type of cmake from experimental to optional?
     9 - giving this ticket a positive review.
     10
     11Then, leave sed improvements to spkg-install of gcc to another ticket?