Hi, today we experienced a couple of issues where pants wasn't able to find gcc (required by one 3rd party dependency) when preparing the pex. We got it working adding

/usr/bin

to

interpreter_search_paths

I suspect it's not using the correct PATH, have you ever seen this sort of issue?

Hi Fede, what Pants version are you using? The answer changes a little depending on that.

1.30 and only the v2 engine

Got it. The answer isn’t very satisfying in 1.30 -

interpreter_search_paths

is used both for discovering interpreters and for setting the $PATH. In 2.0.0.dev7, we cleaned that up by adding a new option called

--pex-executable-search-paths

, which is what’s used to set the $PATH for any subprocess that is run for the Python pipeline.

--python-setup-interpreter-search-paths

is now solely used for discovering the

python

binary. We’re pushing to get out

2.0.0.alpha0

out soon. Is your current approach working alright in 1.30, even though it’s not ideal?

yes, it's working. I wasn't sure why and if it was the correct approach. thanks for the help and for the details 🙂 I'll give a try to 2.0.0 soon