tfenv icon indicating copy to clipboard operation
tfenv copied to clipboard

macOS / arm64

Open cdaguerre opened this issue 4 years ago • 6 comments
trafficstars

In case someone else wonders, tfenv does support ARM architecture on macOS when setting a TFENV_ARCH env var to arm64. As @kamatama41 said in the MR that introduced this env var, it should probably be resolved using uname -m rather than defaulting to amd64

cdaguerre avatar Oct 29 '21 13:10 cdaguerre

hi, this was very informative and helpful. when can we expect this to get merged?

BrianMusson avatar Nov 23 '21 18:11 BrianMusson

@BrianMusson this is already merged, you can use it like this:

TFENV_ARCH=arm64 tfenv install 1.0.2

Note that 1.0.2 is the first release that was compiled for macOS arm64. Earlier versions will fail with a 403 error.

danielcompton avatar Dec 06 '21 03:12 danielcompton

@danielcompton yea, that works, but it would be nice if install would automatically know which arch to use :)

Though it seems that that's already the case as of https://github.com/tfutils/tfenv/commit/d22ffb421ec8e6263fe0dd5ba705bd2cc386960e and https://github.com/tfutils/tfenv/commit/abd0f46ca658dc81ec4f253f4883c7b942f8f1dd, but those commits weren't released (yet); so I guess all we have to do is to wait for next release to happen (and set local TFENV_ARCH env variable in the time being, as you suggest).

kblcuk avatar Dec 07 '21 12:12 kblcuk

Just ran into this, and following the README.md I used arm at first, until I realized it needs to be arm64. I just added:

export TFENV_ARCH=arm64

Into my ~/.zshrc

nodesocket avatar Feb 05 '22 20:02 nodesocket

It would be nice if 'tfenv' either didn't show anything older than 1.0.2 when used on Mac arm64 or just displayed a warning about this.

cron410 avatar Mar 24 '22 20:03 cron410

Or better yet, would fetch and compile older versions upon request when it hits a 404 on the precompiled binary.

cron410 avatar Mar 30 '22 01:03 cron410