Skip to content
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 PATH is Broken on Mac High Sierra #10304

Closed
liangfok opened this issue Dec 21, 2018 · 6 comments · Fixed by #10305
Closed

Python PATH is Broken on Mac High Sierra #10304

liangfok opened this issue Dec 21, 2018 · 6 comments · Fixed by #10305
Assignees

Comments

@liangfok
Copy link
Contributor

liangfok commented Dec 21, 2018

See the errors here:

https://drake-jenkins.csail.mit.edu/view/Nightly%20Production/job/mac-high-sierra-unprovisioned-clang-bazel-nightly-release/35/

env: python2: No such file or directory
...
//:py/install_test                                                       FAILED in 0.9s

This is likely due to a Bazel update. An RC file likely needs the following to be added:

--action_env=PATH=/usr/local/bin:/usr/bin:/bin
@jamiesnape
Copy link
Contributor

Relates bazelbuild/bazel#6648.

@EricCousineau-TRI
Copy link
Contributor

Would adding this to install_prereqs_user_environment for Mac make it work?

@jamiesnape
Copy link
Contributor

It would, though technically this is not a Mac issue.

@jamiesnape
Copy link
Contributor

jamiesnape commented Dec 21, 2018

I imagine the analog for Linux would be --action_env=PATH=/usr/bin:/bin.

@EricCousineau-TRI EricCousineau-TRI self-assigned this Dec 21, 2018
@jamiesnape
Copy link
Contributor

I think this also makes our own version of the bzl which() function redundant, but that is not going to break anything.

@jwnimmer-tri
Copy link
Collaborator

jwnimmer-tri commented Dec 21, 2018

I think this also makes our own version of the bzl which() function redundant, but that is not going to break anything.

Not quite?

(1) When our //tools/workspace rules are used from a bazel_drake_external, we don't know what the action $PATH will be. I think its still good to ignore whatever the user configured, at least by default.

(2) I'm not sure that rcfile build --action_env affects, e.g., bazel fetch //....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants