# Installer does not add forc **URL:** \ **Category:** Tooling and IDE\ **Created:** [March 29, 2023, 6:52pm UTC](https://forum.fuel.network/t/installer-does-not-add-forc/2185 "2023-03-29T18:52:40Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![tibi77](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/tibi77/32/1220_2.png) [@tibi77](https://forum.fuel.network/u/tibi77)\ **Post date:** [March 29, 2023, 6:52pm UTC](https://forum.fuel.network/t/installer-does-not-add-forc/2185/1 "2023-03-29T18:52:40Z")
Hey! I used the install command from the fuelup repo and even though the install got through, i can not run the forc rc command installed with : `curl --proto '=https' --tlsv1.2 -sSf https://install.fuel.network/fuelup-init.sh | sh` using macos 13.2.1 (22D68) ---
**Author:** ![Voxelot](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/voxelot/32/12_2.png) [@Voxelot](https://forum.fuel.network/u/Voxelot)\ **Post date:** [March 29, 2023, 9:36pm UTC](https://forum.fuel.network/t/installer-does-not-add-forc/2185/2 "2023-03-29T21:36:02Z")
Is there a specific forc sub-command that isn’t working or is forc not found at all in your terminal? An alternative way to install forc is to use `cargo install forc`. The caveat of installing via cargo is that it is has to compile from scratch and you’ll have to ensure the version you’ve installed is compatible with the testnet you’re targeting. It’s worth double checking if you have forc installed into your local `~/.fuelup/bin` directory. If so, then you should also double check that the fuelup directory is added to your `PATH` environment variable. ---
**Author:** ![mindtree](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/mindtree/32/5_2.png) [@mindtree](https://forum.fuel.network/u/mindtree)\ **Post date:** [March 29, 2023, 11:03pm UTC](https://forum.fuel.network/t/installer-does-not-add-forc/2185/3 "2023-03-29T23:03:28Z")
> [@Voxelot](#): > > It’s worth double checking if you have forc installed into your local `~/.fuelup/bin` directory. If so, then you should also double check that the fuelup directory is added to your `PATH` environment variable. Yeah fuelup should prompt about this on the initial install. You can `echo $PATH` to see if the `~/.fuelup/bin` directory is on there. ---
**Author:** ![tibi77](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/tibi77/32/1220_2.png) [@tibi77](https://forum.fuel.network/u/tibi77)\ **Post date:** [March 30, 2023, 11:21am UTC](https://forum.fuel.network/t/installer-does-not-add-forc/2185/4 "2023-03-30T11:21:44Z")
```auto ~ ls .fuelup/bin/forc* .fuelup/bin/forc-explore .fuelup/bin/forc-index .fuelup/bin/forc-wallet ``` ```auto ~ forc zsh: command not found: forc ``` ```auto ~ echo $PATH | grep fuel /Users/tiberiulepadatu/.fuelup/bin:... ``` Checked all of them, seems that I have them in there ---
**Author:** ![bingcicle](https://avatars.discourse-cdn.com/v4/letter/b/b2d939/32.png) [@bingcicle](https://forum.fuel.network/u/bingcicle)\ **Post date:** [March 30, 2023, 1:52pm UTC](https://forum.fuel.network/t/installer-does-not-add-forc/2185/5 "2023-03-30T13:52:09Z")
That output looks to me like the forc download didn’t succeed 🤔 Could you: 1. do `ls ~/.fuelup/store` and see what output you get? 2. retry the installation step again and post the full output? 3. If all else fails, we could also manually download the binaries from the GitHub release itself, but that would involve some manual steps. Could you see of 1) and 2) works for you first? ---
**Author:** ![tibi77](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/tibi77/32/1220_2.png) [@tibi77](https://forum.fuel.network/u/tibi77)\ **Post date:** [March 30, 2023, 2:17pm UTC](https://forum.fuel.network/t/installer-does-not-add-forc/2185/6 "2023-03-30T14:17:12Z")
```auto ~ ls ~/.fuelup/store forc-0.35.5 forc-explore-0.28.1 forc-index-0.6.0 forc-index-0.6.1 forc-wallet-0.2.1 fuel-core-0.17.3 fuel-core-0.17.4 fuel-indexer-0.6.0 fuel-indexer-0.6.1 ``` ---
**Author:** ![tibi77](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/tibi77/32/1220_2.png) [@tibi77](https://forum.fuel.network/u/tibi77)\ **Post date:** [March 30, 2023, 2:18pm UTC](https://forum.fuel.network/t/installer-does-not-add-forc/2185/7 "2023-03-30T14:18:31Z")
did the 1,2 also did `cargo install` and I have the same behaviour ---
**Author:** ![bingcicle](https://avatars.discourse-cdn.com/v4/letter/b/b2d939/32.png) [@bingcicle](https://forum.fuel.network/u/bingcicle)\ **Post date:** [March 30, 2023, 2:31pm UTC](https://forum.fuel.network/t/installer-does-not-add-forc/2185/8 "2023-03-30T14:31:25Z")
OK, from that output it seems like the binaries were indeed installed to `~/.fuelup/store/forc-0.35.5` - could you `ls` that and see if you find `forc` there? Since it’s there, I’m assuming the binaries were properly installed - try linking `fuelup` to `forc` by doing `ln -s ~/.fuelup/bin/fuelup ~/.fuelup/bin/forc`, and try executing forc again. ---
**Author:** ![tibi77](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/tibi77/32/1220_2.png) [@tibi77](https://forum.fuel.network/u/tibi77)\ **Post date:** [March 30, 2023, 2:47pm UTC](https://forum.fuel.network/t/installer-does-not-add-forc/2185/9 "2023-03-30T14:47:45Z")
I just have a tar in that ls ```auto ls ~/.fuelup/store/forc-0.35.5 forc-0.35.5-darwin_amd64.tar.gz ``` ---
**Author:** ![bingcicle](https://avatars.discourse-cdn.com/v4/letter/b/b2d939/32.png) [@bingcicle](https://forum.fuel.network/u/bingcicle)\ **Post date:** [March 30, 2023, 3:13pm UTC](https://forum.fuel.network/t/installer-does-not-add-forc/2185/10 "2023-03-30T15:13:28Z")
> [@tibi77](#): > > ```auto > ls ~/.fuelup/store/forc-0.35.5 > forc-0.35.5-darwin_amd64.tar.gz > > ``` Oh, one thing you could also do is to use fuelup to install the binaries now since you have it (I’m assuming?) `fuelup toolchain install latest`. If that doesn’t work too I think you might have to manually use `tar` to unpack the tarball. ---
**Author:** ![tibi77](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/tibi77/32/1220_2.png) [@tibi77](https://forum.fuel.network/u/tibi77)\ **Post date:** [March 30, 2023, 4:45pm UTC](https://forum.fuel.network/t/installer-does-not-add-forc/2185/11 "2023-03-30T16:45:10Z")
So just checked now. The tar is actually empty… ```auto ls -la total 0 drwxr-xr-x 3 tiberiulepadatu staff 96 Mar 29 15:15 . drwxr-xr-x 11 tiberiulepadatu staff 352 Mar 29 15:44 .. -rw-r--r-- 1 tiberiulepadatu staff 0 Mar 29 15:15 forc-0.35.5-darwin_amd64.tar.gz ``` ---
**Author:** ![tibi77](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/tibi77/32/1220_2.png) [@tibi77](https://forum.fuel.network/u/tibi77)\ **Post date:** [March 30, 2023, 4:45pm UTC](https://forum.fuel.network/t/installer-does-not-add-forc/2185/12 "2023-03-30T16:45:41Z")
Already ran that `fuelup toolchain install latest` . ---
**Author:** ![bingcicle](https://avatars.discourse-cdn.com/v4/letter/b/b2d939/32.png) [@bingcicle](https://forum.fuel.network/u/bingcicle)\ **Post date:** [March 30, 2023, 5:33pm UTC](https://forum.fuel.network/t/installer-does-not-add-forc/2185/13 "2023-03-30T17:33:24Z")
OK, you might have to try the manual installation step here if you want to use fuelup unfortunately 😕 1. Download the correct tarball from [Release v0.35.5 · FuelLabs/sway · GitHub](https://github.com/FuelLabs/sway/releases/tag/v0.35.5) 2. extract it into where you just found the empty tarball, i.e. ~/.fuelup/store/forc-0.35.5 (this is how fuelup finds your binaries) 3. running `fuelup toolchain install latest` again should link the existing binaries into your toolchain directory at ~/.fuelup/toolchains/latest-…/bin Sorry for the trouble! Were there any useful output when the download seemingly failed? This could help us in finding out what’s wrong. ---
**Author:** ![sarah](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/sarah/32/13_2.png) [@sarah](https://forum.fuel.network/u/sarah)\ **Post date:** [April 26, 2023, 2:40pm UTC](https://forum.fuel.network/t/installer-does-not-add-forc/2185/16 "2023-04-26T14:40:49Z")