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
Fresh install of macOS Sonoma 14.2.1 on MacBookPro M1 Max
./build.sh reports:
…
checking for ranlib... /usr/bin/ranlib
checking for gsed... no
configure: error: gsed must be available to build this library
…
I then did `brew install gsed` and got further:
…
checking for PTHREAD_PRIO_INHERIT... yes
checking for asm/page.h... no
checking for python... no
configure: error: Cannot find python in your system path
I then did `brew install python3`, same error. I presume that python3 is not symlinked as `keytool-cli` expects.
So I deleted and recloned the repo, but it is still not working as of 2023-01-31 commit 4c45a67:
% ./build.sh
…
checking whether pthreads work with "-pthread" and "-lpthread"... yes
checking whether Clang needs flag to prevent "argument unused" warning when linking with -pthread... no
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking whether more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... yes
checking for asm/page.h... no
checking for pkg-config... /opt/homebrew/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for python... no
configure: error: Cannot find python in your system path
So I confirmed that python3 was in path, and aliases python to it:
% which python
python not found
% which python3
/opt/homebrew/bin/python3
% alias python='/opt/homebrew/bin/python3'
% which python
python: aliased to /opt/homebrew/bin/python3
% python --version
Python 3.11.7
However, the result still is:
% ./build.sh
…
checking for asm/page.h... no
checking for pkg-config... /opt/homebrew/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for python... no
configure: error: Cannot find python in your system path
%
Activity
ChristopherA commentedon Jan 31, 2024
So I deleted and recloned the repo, but it is still not working as of 2023-01-31 commit 4c45a67:
So I confirmed that
python3was in path, and aliasespythonto it:However, the result still is: