@@ -291,7 +291,7 @@ Setting up gitian images
291291-------------------------
292292
293293Gitian needs virtual images of the operating system to build in.
294- Currently this is Ubuntu Precise for both x86 architectures .
294+ Currently this is Ubuntu Precise for x86_64 .
295295These images will be copied and used every time that a build is started to
296296make sure that the build is deterministic.
297297Creating the images will take a while, but only has to be done once.
@@ -300,7 +300,6 @@ Execute the following as user `debian`:
300300
301301``` bash
302302cd gitian-builder
303- bin/make-base-vm --lxc --arch i386 --suite precise
304303bin/make-base-vm --lxc --arch amd64 --suite precise
305304```
306305
@@ -311,33 +310,25 @@ There will be a lot of warnings printed during build of the images. These can be
311310Getting and building the inputs
312311--------------------------------
313312
314- In [ doc/release-process.md] ( release-process.md ) in the bitcoin repository under 'Fetch and build inputs'.
315- you will find a list of ` wget ` commands that can be executed to get the dependencies.
313+ Follow the instructions in [ doc/release-process.md] ( release-process.md ) in the bitcoin repository
314+ under 'Fetch and build inputs' to install sources which require manual intervention. Also follow
315+ the next step: 'Seed the Gitian sources cache', which will fetch all necessary source files allowing
316+ for gitian to work offline.
316317
317- I needed to add ` --no-check-certificate ` to the OpenSSL wget line to make it work.
318- Likely this is because the ca-certificates in Debian 7.4 is fairly old. This does not create a
319- security issue as the gitian descriptors check the integrity of the input archives and refuse to work
320- if any one is corrupted.
318+ Building Bitcoin
319+ ----------------
321320
322- After downloading the archives, execute the ` gbuild ` commands to build the dependencies.
323- This can take a long time, but only has to be done when the dependencies change, for example
324- to upgrade the used version.
321+ To build Bitcoin (for Linux, OSX and Windows) just follow the steps under 'perform
322+ gitian builds' in [ doc/release-process.md] ( release-process.md ) in the bitcoin repository.
325323
326- ** Note ** : Do not forget to copy the result from ` build/out ` to ` inputs ` after every gbuild command! This will save
327- you a lot of time .
324+ This may take a long time as it also builds the dependencies needed for each descriptor.
325+ These dependencies will be cached after a successful build to avoid rebuilding them when possible .
328326
329327At any time you can check the package installation and build progress with
330328
331329``` bash
332330tail -f var/install.log
333331tail -f var/build.log
334- ```
335-
336- Building Bitcoin
337- ----------------
338-
339- To build Bitcoin (for Linux, OSX and Windows) just follow the steps under 'perform
340- gitian builds' in [ doc/release-process.md] ( release-process.md ) in the bitcoin repository.
341332
342333Output from ` gbuild` will look something like
343334
@@ -348,7 +339,7 @@ Output from `gbuild` will look something like
348339 Resolving deltas: 100% (25724/25724), done.
349340 From https://github.com/bitcoin/bitcoin
350341 ... (new tags, new branch etc)
351- --- Building for precise i386 ---
342+ --- Building for precise x86_64 ---
352343 Stopping target if it is up
353344 Making a new image copy
354345 stdin: is not a tty
@@ -363,9 +354,6 @@ Output from `gbuild` will look something like
363354 lxc-start: Connection refused - inotify event with no name (mask 32768)
364355 Running build script (log in var/build.log)
365356
366- As when building the dependencies, the progress of package installation and building
367- can be inspected in ` var/install.log ` and ` var/build.log ` .
368-
369357Building an alternative repository
370358-----------------------------------
371359
0 commit comments