install-qt-action: Action failing on macOS 10.15

Hello, I tried to use install-qt-action to get qt on macOS 10.15 runner. The step is failing:

brew install p7zip
Warning: p7zip 16.02_2 is already installed and up-to-date
To reinstall 16.02_2, run `brew reinstall p7zip`
python3 -m pip install setuptools wheel
Requirement already satisfied: setuptools in /usr/local/lib/python3.9/site-packages (50.3.2)
Requirement already satisfied: wheel in /usr/local/lib/python3.9/site-packages (0.35.1)
python3 -m pip install py7zr==0.10.1
Collecting py7zr==0.10.1
  Downloading py7zr-0.10.1-py3-none-any.whl (62 kB)
Collecting pycryptodome
  Downloading pycryptodome-3.9.9.tar.gz (15.5 MB)
Collecting texttable
  Downloading texttable-1.6.3-py2.py3-none-any.whl (10 kB)
Building wheels for collected packages: pycryptodome
  Building wheel for pycryptodome (setup.py): started
  Building wheel for pycryptodome (setup.py): finished with status 'error'
  ERROR: Command errored out with exit status 1:
   command: /usr/local/opt/python@3.9/bin/python3.9 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/private/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pip-install-7ia01e4_/pycryptodome/setup.py'"'"'; __file__='"'"'/private/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pip-install-7ia01e4_/pycryptodome/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /private/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pip-wheel-u1yfcjec
       cwd: /private/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/pip-install-7ia01e4_/pycryptodome/

https://github.com/dyfer/supercollider/runs/1476959017?check_suite_focus=true#step:8:1

EDIT: I submitted an issue with pycryptodome as well

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 15 (7 by maintainers)

Most upvoted comments

For anyone else running into this on GitHub’s official macOS runners, it turns out that setting MACOSX_DEPLOYMENT_TARGET in your environment will also break it in the same way. I just moved this down to my actual build step, and everything works fine again.