<p>The compiled binaries on the website are built using gitian. This is deterministic so you'll get an identical build to everyone else who has built it, for verification purposes. You can find instructions on how to do this here: <a href="https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md" rel="nofollow noreferrer">https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md</a></p>

CC BY-SA 3.0
2017-10-18T17:06:45.220Z
For the sake of completeness, I add this link, which is also very important:
https://github.com/bitcoin-core/docs/blob/master/gitian-building.md
FedFranz
CC BY-SA 3.0
2017-10-19T16:04:19.813Z
Since I had some troubles in actually completing the building process, I wrote a small guide as a reference:
https://gist.github.com/frz-dev/3e3e906fa06294e61930e81b473e1e5b
FedFranz
CC BY-SA 3.0
2017-10-10T11:46:56.623Z
2017-10-10T11:46:56.623Z
meshcollider
<p>I'm trying to build the same tarball you can download from the website, containing the following filetree:</p>

<pre><code>$ ls -R ../../bitcoin-0.15.0/
../../bitcoin-0.15.0/:
bin  include  lib  share

../../bitcoin-0.15.0/bin:
bitcoin-cli  bitcoind  bitcoin-qt  bitcoin-tx  test_bitcoin

../../bitcoin-0.15.0/include:
bitcoinconsensus.h

../../bitcoin-0.15.0/lib:
libbitcoinconsensus.so  libbitcoinconsensus.so.0  libbitcoinconsensus.so.0.0.0

../../bitcoin-0.15.0/share:
man

../../bitcoin-0.15.0/share/man:
man1

../../bitcoin-0.15.0/share/man/man1:
bitcoin-cli.1  bitcoind.1  bitcoin-qt.1  bitcoin-tx.1
</code></pre>

<p>I'm using the 'prefix' configure to put the binaries into a specific folder</p>

<pre><code>./configure --prefix=/home/ff/bitcoin-build
</code></pre>

<p>Now, the content I get inside the target directory is almost the same (there are some files more). However,when I try to copy and run it inside a container it gives me an error (which is not the case with the original tarball).</p>

<p>So, my question is: how do I build the sources in order to produce the same tarball you get from the website?</p>

<bitcoin-core><compiling><gitian>
How to build Bitcoin Core Linux tarball from sources
FedFranz
# How to build Bitcoin Core Linux tarball from sources

(Asked by: username_0 on 2017-10-10)

I'm trying to build the same tarball you can download from the website, containing the following filetree:

```
$ ls -R ../../bitcoin-0.15.0/
../../bitcoin-0.15.0/:
bin  include  lib  share

../../bitcoin-0.15.0/bin:
bitcoin-cli  bitcoind  bitcoin-qt  bitcoin-tx  test_bitcoin

../../bitcoin-0.15.0/include:
bitcoinconsensus.h

../../bitcoin-0.15.0/lib:
libbitcoinconsensus.so  libbitcoinconsensus.so.0  libbitcoinconsensus.so.0.0.0

../../bitcoin-0.15.0/share:
man

../../bitcoin-0.15.0/share/man:
man1

../../bitcoin-0.15.0/share/man/man1:
bitcoin-cli.1  bitcoind.1  bitcoin-qt.1  bitcoin-tx.1

```

I'm using the 'prefix' configure to put the binaries into a specific folder

```
./configure --prefix=/home/ff/bitcoin-build

```

Now, the content I get inside the target directory is almost the same (there are some files more). However,when I try to copy and run it inside a container it gives me an error (which is not the case with the original tarball).

So, my question is: how do I build the sources in order to produce the same tarball you get from the website?

**Tags:** bitcoin-core, compiling, gitian


---

## 1 answers

### Answer by username_1 on 2017-10-10. Score: 1 | Accepted answer

The compiled binaries on the website are built using gitian. This is deterministic so you'll get an identical build to everyone else who has built it, for verification purposes. You can find instructions on how to do this here: <https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md>

> **Comments:**
> **username_0**: For the sake of completeness, I add this link, which is also very important: https://github.com/bitcoin-core/docs/blob/master/gitian-building.md  
> **username_0**: Since I had some troubles in actually completing the building process, I wrote a small guide as a reference: https://gist.github.com/frz-dev/3e3e906fa06294e61930e81b473e1e5b  

---

