1 2016-11-02 12:31:18 <rafalcpp> Hello, does anyone know the exact flags to use in boost compilation inside Gitian when targeting Mac OS X? The build process seems to delete boost sources and configs after it's done making it a bit less easy to debug the process
 2 2016-11-02 12:33:49 <jonasschnelli> rafalcpp: did you checked the build.log inside the gitian-builder/logs dir?
 3 2016-11-02 12:38:13 <rafalcpp> jonasschnelli: yes, it does not contain the exact b2 invocation, nor the content of file user-config.jam
 4 2016-11-02 12:38:50 <rafalcpp> can try to read them based on ./inputs/bitcoin/depends/packages/boost.mk sources, but I would rather log inside Gitian (on-target) and run few tests regarding building boost manually
 5 2016-11-02 12:39:28 <jonasschnelli> rafalcpp: AFAIK boost is also cached once it was successfully built over depends/
 6 2016-11-02 12:40:06 <rafalcpp> jonasschnelli: I can not find the boost sources anywhere inside the Gitian, any idea what code removes them?
 7 2016-11-02 12:41:09 <jonasschnelli> rafalcpp: I guess the depends/ compile system throws away the source once it was compiled successfully...
 8 2016-11-02 12:41:28 <jonasschnelli> I think you could change this line: https://github.com/bitcoin/bitcoin/blob/master/contrib/gitian-descriptors/gitian-osx.yml#L94
 9 2016-11-02 12:41:39 <jonasschnelli> rafalcpp: you could add a -V=1 (or is it just -V)
10 2016-11-02 12:41:52 <jonasschnelli> you would get more infos about the boost compilation
11 2016-11-02 12:41:57 <jonasschnelli> (hopefully)
12 2016-11-02 12:42:04 <rafalcpp> hah yes, everyone always forgets is it -V or what, to gnu make ;)
13 2016-11-02 12:42:31 <rafalcpp> jonasschnelli: ok.  Btw I do not see the "rm" that would kill depends anywhere in that .yml
14 2016-11-02 12:43:02 <jonasschnelli> rafalcpp: the rm would/must be in depends/Makefile (or functions.mk)
15 2016-11-02 12:43:22 <jonasschnelli> rafalcpp: https://github.com/bitcoin/bitcoin/blob/master/depends/Makefile#L152
16 2016-11-02 12:43:39 <jonasschnelli> you could remove that part and analyze the sources after the build?
17 2016-11-02 12:43:50 <rafalcpp> oki
18 2016-11-02 13:15:44 <rafalcpp> jonasschnelli: isn't that line just deleting the sources before build, not after build?
19 2016-11-02 13:16:11 <jonasschnelli> rafalcpp: yes. Maybe...
20 2016-11-02 13:16:51 <jonasschnelli> rafalcpp: maybe its here: https://github.com/bitcoin/bitcoin/blob/master/depends/funcs.mk#L200
21 2016-11-02 13:17:05 <jonasschnelli> happy searching... :)
22 2016-11-02 13:24:54 <rafalcpp> in other project we developed more user friendly (I hope) approch to Gitian, you can easily go on-target and there run the script as in yml (or parts of it), great for debugging Gitian issues
23 2016-11-02 13:25:14 <rafalcpp> would we want thigs kind of changes for Bitcoin as well
24 2016-11-02 13:27:54 <jonasschnelli> rafalcpp: I think it would be great if there would be a VM-less way to build deterministic... but not sure if that would be possible
25 2016-11-02 13:28:11 <jonasschnelli> rafalcpp: but you can ssh to the VM and execute a script or fiddle around
26 2016-11-02 13:28:25 <jonasschnelli> (don't ask me how but I know it's possible)
27 2016-11-02 13:31:45 <rafalcpp> jonasschnelli: could be possible, debian deterministic for example.  But one issue is version of compiler. Maybe if user would first build compilere from sources.
28 2016-11-02 13:32:12 <rafalcpp> debian achieved this but inside 1 distro.  Doing it for everyone on any distro on any computer is harder ;)
29 2016-11-02 13:34:09 <rafalcpp> jonasschnelli: after changing sources, you just run gbuild again? it starts over and takes lot of time right? or is there faster way with this gitian?
30 2016-11-02 13:34:48 <jonasschnelli> rafalcpp: I guess there are faster ways.. but the time to find these are probably larger then just compiling again.
31 2016-11-02 13:34:58 <jonasschnelli> Also be aware of depends/inputs/bitcoin
32 2016-11-02 13:35:11 <jonasschnelli> (=make sure your cache is invalidated)