You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can’t build for Python 2.7.10 or 3.4.8 on my Mac or on the GitHub macos-10.15 virtual machine. Installation fails with compilation error, apparently because of wrong version of SSL library.
remove sdist step and use of pyenv
verify unnecessary
[Errno 63] File name too long (circular file path?)
try pip wheel from esig and esig/build
new build script for 2.7 only initially
use virtualenv directly without pyenv
remove virtual environment after use
new GitHub job without 3.5 installation step in build-OSX-python-2.7.yml
extract $p from python –version so will work with 3.4 too
consolidate temporary folder structure
new GitHub job to run 2.7 build script in a Python 3.4 environment ❌ (3.4 not supported)
experiment with dropping pyenv:
with Python 2.7, run python -m pip install -U pip virtualenv
fails with ERROR:root:code for hash md5 was not found., probably to do with my openssl shenanigans:
brew reinstall python@2
FormulaUnavailableError: No available formula with the name “/usr/local/opt/python@2/.brew/python@2.rb”
save python@2.rb locally then brew reinstall python@2.rb
Anaconda experiment to have multiple Python versions without requiring pyenv, at least for 2.7 and 3.4:
install Anaconda for Python 3.7
install Python 2.7 virtual environment
install Python 3.4 virtual environment
PackagesNotFoundError: The following packages are not available from current channels: python=3.4.8
put libressl-2.2.7 somewhere local using curl -O https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-2.2.7.tar.gz then tar xvf libressl-2.2.7.tar.gz
try setting CFLAGS include dir to libressl-2.2.7 - failed, argument not passed to clang, this code which ignores CFLAGS is probably relevant, also homebrew bumped openssl from 1.0 to 1.1 on 27 Nov 2019
try ln -s ~/Repo/esig/build/OSX/libressl-2.2.7 /usr/local/opt/openssl@1.1 - seems to unstick compiler but fails with linker error ld: library not found for -lssl
copy /usr/local/opt/openssl@1.1/lib/* to libressl-2.2.7/lib - seems to unstick that link step, but fails with another linker error ld: framework not found QuickTime (and also highly dubious!)
improve slightly by instead trying ln -s ~/Repo/esig/build/OSX/libressl-2.2.7/include /usr/local/opt/openssl@1.1/include (linking include dir only) - should reproduce QT error
apparently --no-opencv will drop the QT requirement but not sure what this needs to be passed to ❌ – no need to continue this inquiry as no longer trying to build 2.7 from sources
set brew installations to specific versions - probably possible by pointing to specific .rb files but prob unnecessary
upgrade pyenv-virtualenv to 1.1.5 fails because openssl not symlinked??
remove anaconda installation so openssl isn’t picked up from there
removing anaconda means Python falls back to default 2.7 installation that comes with MacOS, and pip fails with ERROR:root:code for hash md5 was not found
reinstall system-level Python 3:
requires xcode-select –install (thought I already did that?)
brew install python3
try with Python 2.7.1 and 2.7.17 - still fails
The text was updated successfully, but these errors were encountered:
Can’t build for Python 2.7.10 or 3.4.8 on my Mac or on the GitHub
macos-10.15
virtual machine. Installation fails with compilation error, apparently because of wrong version of SSL library.sdist
step and use ofpyenv
[Errno 63] File name too long
(circular file path?)pip wheel
fromesig
andesig/build
virtualenv
directly withoutpyenv
build-OSX-python-2.7.yml
$p
frompython –version
so will work with 3.4 toopyenv
:python -m pip install -U pip virtualenv
ERROR:root:code for hash md5 was not found.
, probably to do with myopenssl
shenanigans:brew reinstall python@2
FormulaUnavailableError: No available formula with the name “/usr/local/opt/python@2/.brew/python@2.rb”
python@2.rb
locally thenbrew reinstall python@2.rb
pyenv
, at least for 2.7 and 3.4:PackagesNotFoundError: The following packages are not available from current channels: python=3.4.8
conda create -n myenv python=3.4 -c conda-forge
RuntimeError: Python 3.5 or later is required
fatal error: ‘string’ file not found: #include <string>
CPATH=/Users/rperera/anaconda3/envs/py35/include/c++/v1/
before wheel buildld: warning: directory not found for option ‘-L/opt/local/lib/’; ld: library not found for -lstdc++
pyenv install
)discuss PyPI download statistics with Terrymac-build
branch onlyenable SSH access to GitHub Actions build– haven’t needed it yet_ssl.c:684:35: error: incomplete definition of type ‘struct X509_name_entry_st’
(same error with Python 2.7 and 3.4) ❌libressl-2.2.7
somewhere local usingcurl -O https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-2.2.7.tar.gz
thentar xvf libressl-2.2.7.tar.gz
CFLAGS
include dir tolibressl-2.2.7
- failed, argument not passed to clang, this code which ignoresCFLAGS
is probably relevant, also homebrew bumpedopenssl
from 1.0 to 1.1 on 27 Nov 2019ln -s ~/Repo/esig/build/OSX/libressl-2.2.7 /usr/local/opt/openssl@1.1
- seems to unstick compiler but fails with linker errorld: library not found for -lssl
/usr/local/opt/openssl@1.1/lib/*
tolibressl-2.2.7/lib
- seems to unstick that link step, but fails with another linker errorld: framework not found QuickTime
(and also highly dubious!)ln -s ~/Repo/esig/build/OSX/libressl-2.2.7/include /usr/local/opt/openssl@1.1/include
(linking include dir only) - should reproduce QT errorQuicktime.framework
openssl
- later problem with ImportError: No module named zippset- probably possible by pointing to specificbrew
installations to specific versions.rb
files but prob unnecessarypyenv-virtualenv
to 1.1.5fails because openssl not symlinked??anaconda
installation soopenssl
isn’t picked up from thereanaconda
means Python falls back to default 2.7 installation that comes with MacOS, andpip
fails withERROR:root:code for hash md5 was not found
xcode-select –install
(thought I already did that?)brew install python3
The text was updated successfully, but these errors were encountered: