Hello I m trying to build Pants on an M1 and I ve got the la

Question

Hello I m trying to build Pants on an M1 and I ve got the latest master so even running under rosetta it s using the correct venv Currently it looks like Rust is consistently building under the wrong architecture ```chrisjrn chrisjrns MacBook Pro pants lipo info Users chrisjrn src pants src python pants engine internals native engine pyo3 so Non fat file Users chrisjrn src pants src python pants engine internals native engine pyo3 so is architecture arm64```

ancient-vegetable-10556 · Answer

Continuing a discussion with < witty crayon 22786>

ancient-vegetable-10556 · Answer

and I see that even when I uninstall the arm toolchain from `rustup` the boostrap process re installs it ```chrisjrn chrisjrns MacBook Pro pants MODE=debug pants === 00 01 Building native engine === === 00 01 Building native engine so === info syncing channel updates for 1 52 1 aarch64 apple darwin ```

witty-crayon-22786 · Answer

your goal right now is to fully emulate

ancient-vegetable-10556 · Answer

Right now yes

ancient-vegetable-10556 · Answer

I can expand to running under arm architecture later

witty-crayon-22786 · Answer

ok cc < hundreds father 404> because he might be able to chime in on his strategy when he s available

ancient-vegetable-10556 · Answer

at the very least making things work in a multi arch situation like this will probably solve some problems for other people too

witty-crayon-22786 · Answer

and what is the current content of the `rust toolchain` file the `target` continues to seem very relevant

ancient-vegetable-10556 · Answer

``` toolchain channel = 1 52 1 components = cargo clippy rust std rustc rustfmt targets = x86 64 apple darwin ```

witty-crayon-22786 · Answer

ok interesting so maybe that doesn t override the target that is explicitly passed to cargo

ancient-vegetable-10556 · Answer

surprise

ancient-vegetable-10556 · Answer

This seems to come before cargo

ancient-vegetable-10556 · Answer

``` chrisjrn chrisjrns MacBook Pro pants MODE=debug pants === 00 01 Building native engine === === 00 01 Building native engine so === info syncing channel updates for 1 52 1 aarch64 apple darwin info latest update on 2021 05 10 rust version 1 52 1 9bc8c42bb 2021 05 09 info downloading component cargo ```

witty-crayon-22786 · Answer

you could try adding a ``` build target = x86 64 apple darwin``` section around here <https github com pantsbuild pants blob main src rust engine Cargo toml L7>

witty-crayon-22786 · Answer

< ancient vegetable 10556> re before cargo yea i expect that it s going to actually run `cargo` using whatever it thinks the current platform arch is

witty-crayon-22786 · Answer

targets are for the compiled outputs of builds rather than the build tool itself i think

witty-crayon-22786 · Answer

so cargo being aarch is fine as long as cargo is using the relevant target toolchain for the binary it is building

ancient-vegetable-10556 · Answer

Huh so I think it matters that rustup was installed on my machine in arm mode

ancient-vegetable-10556 · Answer

there s probably somewhere else that we need to specify the arch

ancient-vegetable-10556 · Answer

```warning Users chrisjrn src pants src rust engine Cargo toml unused manifest key build```

witty-crayon-22786 · Answer

gt Huh so I think it matters that rustup was installed on my machine in arm mode it shouldn t that s what i m saying i m 98 sure i could use rustup cargo compiled for my current platform to cross compile to a different platform

ancient-vegetable-10556 · Answer

No I mean from the perspective of the defaults that rustup uses

ancient-vegetable-10556 · Answer

anyway that build section was ignored

ancient-vegetable-10556 · Answer

and I got an `so` for the wrong arch

witty-crayon-22786 · Answer

for example to cross compile for the browser you run cargo as x86 but you set a target of `wasm unknown unknown`

ancient-vegetable-10556 · Answer

Yeah I get that I think it s impacting defaults

witty-crayon-22786 · Answer

looks like it needs to go in cargo config rather than the Cargo toml <https github com rust lang cargo issues 4399> so a ` cargo config toml` at the root of the repo

ancient-vegetable-10556 · Answer

let me look

witty-crayon-22786 · Answer

witty-crayon-22786 · Answer

< ancient vegetable 10556> also to take out one variable here you can ~directly invoke cargo with ` cargo` in the root of the repo

ancient-vegetable-10556 · Answer

it s re downloading a pile of deps which seems promising

ancient-vegetable-10556 · Answer

``` Error Must provide PYO3 CROSS LIB DIR environment variable when cross compiling warning build failed waiting for other jobs to finish ```

ancient-vegetable-10556 · Answer

it seems to think it s cross compiling something

witty-crayon-22786 · Answer

is the `arch ` set such that it should not think that

ancient-vegetable-10556 · Answer

let me check

witty-crayon-22786 · Answer

my guess is that it detects target is x but actual platform is y

ancient-vegetable-10556 · Answer

```chrisjrn chrisjrns MacBook Pro pants arch i386 chrisjrn chrisjrns MacBook Pro pants uname Darwin chrisjrn chrisjrns MacBook Pro pants uname m x86 64 chrisjrn chrisjrns MacBook Pro pants ```

witty-crayon-22786 · Answer

taking a step back you made it further than this yesterday you had gotten to plugin loading which is well after this step ie pants was running successfully including native extensions which arch were you targeting in that case

ancient-vegetable-10556 · Answer

Oh all of that was running under arm64

ancient-vegetable-10556 · Answer

the problem was that there were python dependencies that weren t available in arm64 so I switched to x86 64

witty-crayon-22786 · Answer

ok given how much further along you were there i wonder if continuing down that path and disabling plugins if need be wouldn t be easier

witty-crayon-22786 · Answer

right but only plugins can disable those as a workaround

ancient-vegetable-10556 · Answer

Allow me a few minutes to get back to where I was

witty-crayon-22786 · Answer

for example to disable plugins for one run you could set `PANTS PLUGINS= `

ancient-vegetable-10556 · Answer

it doesn t like that slightly smiling face

ancient-vegetable-10556 · Answer

oh I see why

ancient-vegetable-10556 · Answer

yeah that all worked I was able to successfully bootstrap pants on arm

witty-crayon-22786 · Answer

ok great the only downside of disabling the TC plugin in Pants is that you won t be able to use remote caching we should figure that out in the next few weeks if we can but if i had to guess that is also where < hundreds father 404> is currently

ancient-vegetable-10556 · Answer

My hope is that we can figure out this Rust thing at some point

witty-crayon-22786 · Answer

yea maybe if you re able to skip using Rosetta entirely that s good too

ancient-vegetable-10556 · Answer

Right

ancient-vegetable-10556 · Answer

that s going to require dependencies compiled for the right arch

witty-crayon-22786 · Answer

so the fact that Pants is running at all means that they are already compiled for the right arch i think

witty-crayon-22786 · Answer

which means all of this resolved fine <https github com pantsbuild pants blob main 3rdparty python requirements txt>

ancient-vegetable-10556 · Answer

Not the plugins though right

witty-crayon-22786 · Answer

and only the plugins did not hdrhistogram toolchain

witty-crayon-22786 · Answer

correct

ancient-vegetable-10556 · Answer

Right

hundreds-father-404 · Answer

I don t have good reception to see this whole thread But all I do is set PY=python3 9 and PANTS PYTHON SETUP INTERPRETER CONSTRAINTS to 3 9 I do not use Rosetta and the arch command Rust builds an ARM binary

hundreds-father-404 · Answer

I use envrc to set both env vars

hundreds-father-404 · Answer

Oh and I don t need to disable TC plugin anymore now that it works with Py39 I explicitly enable BuildSense and remote cache read and write

ancient-vegetable-10556 · Answer

OK let s see how that goes then

ancient-vegetable-10556 · Answer

I should have clicked that I needed python 3 9 enabled

ancient-vegetable-10556 · Answer

Looks like I already had Python 3 9 enabled and the thing that was failing was the `hdrhistogram` plugin This on the other hand affects the toolchain plugin ```Needed macosx 11 0 arm64 cp 39 cp39 compatible dependencies for 1 cryptography gt =3 2 Required by pyOpenSSL 20 0 1 But this pex had no cryptography distributions 2 cryptography gt =1 3 4 extra == security Required by requests 2 25 1 But this pex had no cryptography distributions ```

hundreds-father-404 · Answer

Oh Run with no process execution local cache as an experiment

ancient-vegetable-10556 · Answer

that didn t help

hundreds-father-404 · Answer

Hm Is there more to the error What command are you running

ancient-vegetable-10556 · Answer

I m running `MODE=debug pants no process execution local cache` I have `hdrhistogram` commented out in my config file and there s one more line that I missed excluding the traceback `pex environment ResolveError Failed to resolve requirements from PEX environment private var folders 0m h2n902qn38b8555xq8z0w h40000gn T process executionSOzQ5z tmp tmpkbur2u36 `

hundreds-father-404 · Answer

What s the traceback

ancient-vegetable-10556 · Answer

``` File Users chrisjrn cache pants named caches pex root unzipped pexes 478cc1fa371ca40aa3e7dafee735ca438d4a243f bootstrap pex pex py line 484 in execute exit value = self wrap coverage self wrap profiling self execute File Users chrisjrn cache pants named caches pex root unzipped pexes 478cc1fa371ca40aa3e7dafee735ca438d4a243f bootstrap pex pex py line 401 in wrap coverage return runner args File Users chrisjrn cache pants named caches pex root unzipped pexes 478cc1fa371ca40aa3e7dafee735ca438d4a243f bootstrap pex pex py line 432 in wrap profiling return runner args File Users chrisjrn cache pants named caches pex root unzipped pexes 478cc1fa371ca40aa3e7dafee735ca438d4a243f bootstrap pex pex py line 540 in execute return self execute entry self pex info entry point File Users chrisjrn cache pants named caches pex root unzipped pexes 478cc1fa371ca40aa3e7dafee735ca438d4a243f bootstrap pex pex py line 656 in execute entry return self execute pkg resources entry point File Users chrisjrn cache pants named caches pex root unzipped pexes 478cc1fa371ca40aa3e7dafee735ca438d4a243f bootstrap pex pex py line 688 in execute pkg resources return runner File Users chrisjrn cache pants named caches pex root unzipped pexes 478cc1fa371ca40aa3e7dafee735ca438d4a243f deps pex 2 1 42 py2 py3 none any whl pex bin pex py line 1161 in main seed info = seed cache options pex verbose=options seed == Seed VERBOSE File Users chrisjrn cache pants named caches pex root unzipped pexes 478cc1fa371ca40aa3e7dafee735ca438d4a243f deps pex 2 1 42 py2 py3 none any whl pex bin pex py line 1215 in seed cache venv pex = ensure venv pex File Users chrisjrn cache pants named caches pex root unzipped pexes 478cc1fa371ca40aa3e7dafee735ca438d4a243f deps pex 2 1 42 py2 py3 none any whl pex pex bootstrapper py line 421 in ensure venv shenbang = populate venv with pex File Users chrisjrn cache pants named caches pex root unzipped pexes 478cc1fa371ca40aa3e7dafee735ca438d4a243f deps pex 2 1 42 py2 py3 none any whl pex tools commands venv py line 117 in populate venv with pex for dist in pex resolve File Users chrisjrn cache pants named caches pex root unzipped pexes 478cc1fa371ca40aa3e7dafee735ca438d4a243f deps pex 2 1 42 py2 py3 none any whl pex pex py line 118 in resolve for dist in env resolve File Users chrisjrn cache pants named caches pex root unzipped pexes 478cc1fa371ca40aa3e7dafee735ca438d4a243f deps pex 2 1 42 py2 py3 none any whl pex environment py line 608 in resolve self resolved dists = self resolve dists all reqs File Users chrisjrn cache pants named caches pex root unzipped pexes 478cc1fa371ca40aa3e7dafee735ca438d4a243f deps pex 2 1 42 py2 py3 none any whl pex environment py line 692 in resolve dists raise ResolveError ```

hundreds-father-404 · Answer

Try renaming or rm rfing ~ cache pants What s happening is the cache has x86 platform in it and now you re using arm64

ancient-vegetable-10556 · Answer

fwiw we merged a fix last week that makes the venvs in the cache be arch specific <https github com pantsbuild pants pull 12192> Is there somewhere else in ` cache` that is arch specific

ancient-vegetable-10556 · Answer

noting that removing the cache did indeed work

witty-crayon-22786 · Answer

there is actually i ll post a fix for that

ancient-vegetable-10556 · Answer

thank you

hundreds-father-404 · Answer

< witty crayon 22786> the fix is to finish my design doc to make platform be arch aware right

witty-crayon-22786 · Answer

uhm mayhaps my fix may have nothing to do with the above

witty-crayon-22786 · Answer

ah so the issue above is that we re not including the full platform arch when invoking PEX

witty-crayon-22786 · Answer

my unrelated fix <https github com pantsbuild pants pull 12201>

hundreds-father-404 · Answer

Yeah the resolve requirements Process stored in lmdb store keeps OS in mind but not arch If we fixed that the subsequent Pex Process should choose the correct repository pex I think the fix is with Pants not Pex Idk Chris s roadmap but this would be an excellent introduction to Pants including a little work on rust I could write up instructions and or video chat

witty-crayon-22786 · Answer

possibly yea we paired on <https github com pantsbuild pants issues 12059> last week so a good next thing maybe