Solaris 11.4 SRU70 (aka 11.4.70.170.1) ncpa310 python-pip failure on pre-reqs
bish0polis opened this issue · 0 comments
Hitting the wall on v2.4.1, I thought of trying a v3 build and seeing how far I got.
Narrator: It wasn't far.
I noticed the Solaris tree was (re)moved from the 3.0 branch. I understand we're back into mostly-unfamiliar territory. Additionally, we're quasi-airgapped here for security. This complicates the "just get this week's release" workflow, which still baffles me - I still have CPAN Dependency-hell PTSD - but we're trying to fake it. Ideally once we can build an installable independent artefact, we'll be golden ... oldies.
Oh. If we're shipping a 3.11.3 python in the v3.1.0 tarball .. I didn't see it. Probably no big deal, but I'm on the system python which is 3.9.19 .
Our evolving process is
- 'edge' host hits the proxy and off to the net to
python -m pip download -r -r require.solaris.txt
or so - ship the tarball of wheels (a wagon of wheels sounds better) in to the build host
- 'build' host does the
python -m pip install -r require.solaris.txt --no-index --find-links /tmp/untarred/wheels
- bobbitt the
update_py
andcommand -v git
bits in build.sh build.sh -S -b
and '.. -p` to make the artefact
Just like momma used to make.
Currently:
python -m pip download \
-d /export/home/bishop/build-ncpa3/pyreqs \
-r <(gtar --wildcards --to-stdout -xzf v3.1.0.tar.gz ncpa-3.1.0/build/resources/require.txt)
Collecting cx_Freeze
Using cached cx_freeze-7.1.1.tar.gz (2.9 MB)
:
[ lots of getting/got/good messages ]
:
Collecting cryptography
Using cached cryptography-42.0.8.tar.gz (671 kB)
Installing build dependencies ... ^[[?25ldone
^[[?25h Getting requirements to build wheel ... ^[[?25lerror
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [45 lines of output]
Traceback (most recent call last):
:
[mom's spaghetti removed; poor rabbit]
:
File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
File "/tmp/pip-build-env-n0puo9jy/overlay/lib/python3.9/site-packages/setuptools_rust/__init__.py", line 1, in <module>
from .build import build_rust
File "/tmp/pip-build-env-n0puo9jy/overlay/lib/python3.9/site-packages/setuptools_rust/build.py", line 22, in <module>
from setuptools.command.build import build as CommandBuild
ModuleNotFoundError: No module named 'setuptools.command.build'
[end of output]
So that's where I am today.
I sense a question about rust. We don't appear to have a rust comterpeter installed, but I suspect one - probably of a 'classic' vintage - may be available from the almighty Oracle. Could it change our behaviour? (Changing edge hosts is costly for paper, so I'm reluctant to Just Test It)
Have we gotten any further than my very brief attempt?