--- Log opened Fri Mar 13 00:00:24 2020
02:48 < hebasto> 1800UTC on Friday? Cool!
04:04 -!- Helmer20Wunsch [~Helmer20W@ns334669.ip-5-196-64.eu] has joined #bitcoin-builds
09:32 -!- billygarrison [2f378fb6@47.55.143.182] has joined #bitcoin-builds
09:42 < dongcarl> Hey hebasto I think Cory is saying Monday works better for him, you down for Monday 1800UTC?
09:43 < billygarrison> Anyone here familiar with building for windows using WSL? I have the same issue as this user: https://github.com/bitcoin/bitcoin/issues/17277 except the error that pops up looks different (mine says "The code execution cannot proceed because libwinpthread-1.dll was not found. Reinstalling the program may fix this problem"). I think it has something
09:43 < billygarrison> to do with zeromq maybe.
09:44 < dongcarl> billygarrison: Looking
09:47 -!- Helmer20Wunsch [~Helmer20W@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 265 seconds]
09:49 < dongcarl> billygarrison: So you're using WSL to run Ubuntu on Windows, and then cross-compiling for windows?
09:49 < dongcarl> Is that correct?
09:49 < billygarrison> Yes that is correct
09:50 < billygarrison> And scratch what I said about zeromq. I could have been mistaken, now it looks like maybe bdb? Which is what Wladimir mentioned in the github issue
09:50 < dongcarl> And you switched to the -posix suffixed toolchain on ubuntu?
09:51 < billygarrison> Yes, I ran `sudo update-alternatives --config x86_64-w64-mingw32-g++ # Set the default mingw32 g++ compiler option to posix.
09:51 < billygarrison> ```  Selection    Path                                   Priority   Status
09:51 < billygarrison> manual mode```
09:52 < dongcarl> Oh does that set both g++ and gcc?
09:52 < billygarrison> I'm not sure
09:53 < dongcarl> check `x86_64-w64-mingw32-gcc -v`
09:53 < billygarrison> Thread model: win32
09:56 < dongcarl> Aha!
09:56 < billygarrison> That sounds promising haha, would I update that with `sudo update-alternatives --config x86_64-w64-mingw32-gcc`
09:56 < dongcarl> Yup, try that
09:57 < dongcarl> This might not fix everything, but we should certainly try
09:57 < billygarrison> `update-alternatives: using /usr/bin/x86_64-w64-mingw32-gcc-posix to provide /usr/bin/x86_64-w64-mingw32-gcc (x86_64-w64-mingw32-gcc) in manual mode
09:58 < billygarrison> Not sure if that warning matters, but I will try to rebuild depends now. Takes a bit but I'll ping you when I have a result
09:58 < billygarrison> Thanks a lot!
09:58 < dongcarl> billygarrison: Sounds good :-)
10:29 < hebasto> dongcarl: Monday is ok
10:29 < dongcarl> hebasto: Cool, will try to confirm with fanquake
10:30 -!- billygarrison [2f378fb6@47.55.143.182] has quit [Remote host closed the connection]
10:33 < hebasto> dongcarl: re :"check `x86_64-w64-mingw32-gcc -v`" do you mean `x86_64-w64-mingw32-g++ -v` ?
10:34 < dongcarl> hebasto: I believe we use both gcc and g++ in our build process, so I wanted to make sure that both were pointed to the posix version
10:35 < hebasto> yes, we use both, but our docs mention posix model only for C++ compiler
10:36 < hebasto> and I successfully do cross-compiling with x86_64-w64-mingw32-gcc in win32 thread model
10:39 < dongcarl> hebasto: Ah you're right
10:40 < dongcarl> But since his problem was with winpthreads, I thought to just try it, couldn't hurt to be consistent :-)
10:43 < hebasto> dongcarl: mind looking into #18331 as it targeted for 0.20 ?
10:43 < gribble> https://github.com/bitcoin/bitcoin/issues/18331 | build: Use git archive as source tarball by hebasto · Pull Request #18331 · bitcoin/bitcoin · GitHub
10:50 -!- billygarrison [2f378fb6@47.55.143.182] has joined #bitcoin-builds
10:50 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 272 seconds]
10:50 < billygarrison> @dongcarl: same issue with the gcc set to posix
10:51 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #bitcoin-builds
10:53 < dongcarl> billygarrison: So let me get this straight, this happens when you build depends or build bitcoin or run bitcoin?
10:54 < billygarrison> building depends
10:54 < billygarrison> @dongcarl: specifically I `cd depends` and `make HOST=x86_64-w64-mingw32`
10:55 < billygarrison> As per the build-windows.md instructions
10:55 < dongcarl> Okay, and can you give me the tail of the build error output? say 30 lines or so?
10:57 < billygarrison> Do you know if there would be a log file for that?
10:59 < billygarrison> The build process doesn't crash or anything like that, I get the error popup and click okay, and then it seems to continue the build
11:01 < billygarrison> @dongcarl: When I build bitcoin it seems to work successfully but when I run `make check` I get a wallet error in the test suite log. Not sure if it's related to this issue or not. Here is info about the make check fail: https://github.com/bitcoin/bitcoin/issues/17277#issuecomment-596254641
11:02 < dongcarl> It's related
11:02 < dongcarl> It's threading
11:03 < dongcarl> can you do `make HOST=x86_64-w64-mingw32 > out.log 2>&1` and perhaps post the out.log somewhere?
11:07 < billygarrison> Sure, again this will take some time (30-60 minutes I think). Thank you
11:08 < billygarrison> What does the `2>&1` do?
11:09 < hebasto> billygarrison: prints *all* error to the log
11:09 < billygarrison> Ok thank you
11:10 < billygarrison> Would running this multiple times cause any issues: `PATH=$(echo "$PATH" | sed -e 's/:\/mnt.*//g') # strip out problematic Windows %PATH% imported var`
11:58 -!- billygarrison [2f378fb6@47.55.143.182] has quit [Remote host closed the connection]
12:27 -!- billygarrison [2f378fb6@47.55.143.182] has joined #bitcoin-builds
12:32 < billygarrison> Okay @dongcarl here is the out.log, it hangs at line 11493 https://gist.githubusercontent.com/billygarrison/10d8d779d6b533446e8c392b973f9aa5/raw/2dfa46cba29ec4351168490be77e9b66537d935f/out.log
12:33 < billygarrison> That's the full log, here is one with just the bdb stuff (hangs on line 283) https://gist.github.com/billygarrison/ebaad2b2f93c8e89281e7a1d2ce9d88b
14:26 -!- billygarrison [2f378fb6@47.55.143.182] has quit [Remote host closed the connection]
14:55 -!- billygarrison [2f378fb6@47.55.143.182] has joined #bitcoin-builds
15:07 < dongcarl> billygarrison: Perhaps you could create a separate issue for this, and we'll keep track of all this in GitHub
15:10 < billygarrison> dongcarl: I can do that, or should we add on to this one https://github.com/bitcoin/bitcoin/issues/17277 (I already commented with my initial details)
15:11 < dongcarl> billygarrison: I think this is possibly unrelated, so let's do a separate thread
15:11 < billygarrison> (y)
15:48 < billygarrison> Ok I created an issue here https://github.com/bitcoin/bitcoin/issues/18348
15:50 < fanquake>  billygarrison: thanks
15:52 < billygarrison> No problem
16:50 -!- billygarrison [2f378fb6@47.55.143.182] has quit [Remote host closed the connection]
16:59 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack]
17:10 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #bitcoin-builds
17:19 < jonatack> is it just me -- building on latest master i'm now seeing a bunch of ./wallet/db.h:22:10: fatal error: db_cxx.h: No such file or directory
17:19 < jonatack> include <db_cxx.h>
17:29 -!- aqua427 [~aqua42@amsterdam3.jp.net] has joined #bitcoin-builds
17:34 -!- aqua42 [~aqua42@amsterdam3.jp.net] has quit [Ping timeout: 240 seconds]
17:34 -!- aqua427 is now known as aqua42
17:35 < jonatack> nvm, i think it's just me after apt updating some things
20:21 -!- phantomcircuit_ [~phantomci@2604:a880:1:20::f2:c001] has joined #bitcoin-builds
20:25 -!- aqua427 [~aqua42@amsterdam3.jp.net] has joined #bitcoin-builds
20:27 -!- hebasto_ [~hebasto@95.164.65.194] has joined #bitcoin-builds
20:28 -!- Netsplit *.net <-> *.split quits: aqua42, phantomcircuit, hebasto
20:29 -!- aqua427 is now known as aqua42
--- Log closed Sat Mar 14 00:00:22 2020