-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python not correctly detected in pkgsrc zone on OmniOS during bootstrap #1
Comments
Can you run with more debugging flags enabled to check if Python 3 is actually used? For example The Python version in the SmartOS / Triton image is 3.7 btw. |
The same goes for my zone, but for good measure I tried with other versions too, including Python 2.7. The output with subcommands (curated a bit):
There's loads of INFO and SUBCOMMAND, so I'm showing you only the beginning and end. Let me know if you need more lines. |
Could you show what is in the generated In the logs it says these generated files are in |
The file gets deleted immediately so I'm unable to get its content. Is there a way to persist those temporary files?
/tmp is mounted on swap with |
I think that file gets generated from |
The output now is:
It seems Bazel is not able to detect the path of Python's executable. If I set |
Good to hear you can get a working build! Isn't there a Python installed in |
Yes there is, both in The problematic part of the template seems to be this:
Which corresponds in execution to:
As you can see |
I am trying to build Bazel in a pkgsrc branded zone on OmniOS. This should be the same as building in a Joyent zone on SmartOS. I follow your steps precisely but I get
Forcing Python3 or Python2 with --host_force_python=PY3 (respectively PY2) results in the exact same error message with py3wrapper.sh and py2wrapper.sh
The text was updated successfully, but these errors were encountered: