<p>This is expected.</p>
<p><code>which</code> only searches for binaries in your <code>$PATH</code> variable (e.g. it needs to be placed in <code>/usr/bin</code> or <code>/usr/local/bin</code> for that). If you didn't put <code>bitcoind</code> there, you'll need to invoke it using the pathname (e.g. <code>./src/bitcoind</code> in the directory that holds it).</p>

CC BY-SA 4.0
2021-09-30T13:54:34.243Z
This is expected after following the instructions in the doc\build-windows.md file? can I add the installation folder (/home/myuser/bitcoin) to PATH?
Rony Tesler
CC BY-SA 4.0
2021-09-30T14:03:01.210Z
@RonyTesler: many open source software allows you to "auto" be added to PATH via /usr/local/bin/ if your run "make install".
Mercedes
CC BY-SA 4.0
2021-09-30T15:46:29.977Z
@Mercedes I already ran 'make install DESTDIR=/mnt/c/workspace/bitcoin' before runnin 'which bitcoind'
Rony Tesler
CC BY-SA 4.0
2021-09-30T15:50:44.553Z
/mnt/DRIVE_LETTER/*/* could be part of WSL's PATH by default, or not. I don't and won't know, I can't answer you.
Mercedes
CC BY-SA 4.0
2021-10-02T02:35:08.987Z
What's the difference between adding /mnt/c/bitcoin to PATH and adding /home/myuser/bitcoin?
Rony Tesler
CC BY-SA 4.0
2021-10-03T15:27:12.913Z
@Mercedes Or should I add '/mnt/c/workspace/bitcoin'? Because I used 'make install DESTDIR=/mnt/c/workspace/bitcoin'
Rony Tesler
CC BY-SA 4.0
2021-10-03T15:46:17.187Z
@RonyTesler if it is installed there, you would want to add there to PATH
Mercedes
CC BY-SA 4.0
2021-09-29T15:42:24.283Z
2021-09-29T15:42:24.283Z
Pieter Wuille
<p>I installed bitcoind using Windows 10 WSL Ubuntu.
I see the bitcoind.exe file in the src directory, but when I run &quot;which bitcoind&quot; I get no output.</p>

<bitcoin-core><bitcoind><windows><installation><wsl>
"which bitcoind" outputs nothing
Rony Tesler
# "which bitcoind" outputs nothing

(Asked by: username_0 on 2021-09-29)

I installed bitcoind using Windows 10 WSL Ubuntu.
I see the bitcoind.exe file in the src directory, but when I run "which bitcoind" I get no output.

**Tags:** bitcoin-core, bitcoind, windows, installation, wsl


---

## 1 answers

### Answer by username_1 on 2021-09-29. Score: 1

This is expected.

`which` only searches for binaries in your `$PATH` variable (e.g. it needs to be placed in `/usr/bin` or `/usr/local/bin` for that). If you didn't put `bitcoind` there, you'll need to invoke it using the pathname (e.g. `./src/bitcoind` in the directory that holds it).

> **Comments:**
> **username_0**: This is expected after following the instructions in the doc\build-windows.md file? can I add the installation folder (/home/myuser/bitcoin) to PATH?  
> **username_2**: @username_0: many open source software allows you to "auto" be added to PATH via /usr/local/bin/ if your run "make install".  
> **username_0**: @username_2 I already ran 'make install DESTDIR=/mnt/c/workspace/bitcoin' before runnin 'which bitcoind'  
> **username_2**: /mnt/DRIVE_LETTER/*/* could be part of WSL's PATH by default, or not. I don't and won't know, I can't answer you.  
> **username_0**: What's the difference between adding /mnt/c/bitcoin to PATH and adding /home/myuser/bitcoin?  
> **username_0**: @username_2 Or should I add '/mnt/c/workspace/bitcoin'? Because I used 'make install DESTDIR=/mnt/c/workspace/bitcoin'  
> **username_2**: @username_0 if it is installed there, you would want to add there to PATH  

---

