Unable to compile bitcore core on WSL #21332

<!-- This issue tracker is only for technical issues related to Bitcoin Core. <!-- Describe the issue -->

I'm unable to compile the bit core code on WSL

I get the error message: CC buffer.lo In file included from buffer.c:94: util-internal.h:490:48: error: operator '<=' has no right operand 490 | #if (EVENT__SIZEOF_SIZE_T <= EVENT__SIZEOF_LONG) | ^ make[2]: *** [Makefile:1806: buffer.lo] Error 1

• System information

<!-- What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)? -->

git clone https://github.com/bitcoin/bitcoin.git

<!-- What type of machine are you observing the error on (OS/CPU and disk type)? -->

Windows 10 Running WSL running Ubantu

@ajgodfrey

Windows 10 Running WSL running Ubantu

What is the wsl -l -v command output in your Windows PowerShell?

FWIW, successfully compiled the current master (b9f41df1ead4b6a83a51fc41966b111c8459c313) on Windows 10.0.19042.804 with WSL Ubuntu 20.04.

@ajgodfrey

Windows 10 Running WSL running Ubantu

What is the wsl -l -v command output in your Windows PowerShell?

Name State Version Ubantu Running 2

FWIW, successfully compiled the current master (b9f41df) on Windows 10.0.19042.804 with WSL Ubuntu 20.04.

I'm running windows 10 with Ubantu 20.04.2 LTS

What is Ubantu?

What is Ubantu?

sorry Ubuntu

@ajgodfrey

Windows 10 Running WSL running Ubantu

What is the wsl -l -v command output in your Windows PowerShell?

Name State Version Ubantu Running 2

Could you try to switch WSL version from 2 to 1?

Ubuntu 20.04

On Wed, Mar 3, 2021 at 5:51 AM Hennadii Stepanov notifications@github.com wrote:

@ajgodfrey https://github.com/ajgodfrey

Windows 10 Running WSL running Ubantu

Is your Ubuntu is 18.04 or 20.04?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bitcoin/bitcoin/issues/21332#issuecomment-789132458, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOMWNROH5MYQQWTGAIV36OLTBUXTVANCNFSM4YONCLAQ .

@ajgodfrey

Did you follow https://github.com/bitcoin/bitcoin/blob/master/doc/build-windows.md#building-for-64-bit-windows:

PATH=$(echo "$PATH" | sed -e 's/:\/mnt.*//g')
sudo bash -c "echo 0 > /proc/sys/fs/binfmt_misc/status"
make -C depends HOST=x86_64-w64-mingw32
...

?

I did, thanks!

On Wed, Mar 3, 2021 at 9:29 AM Hennadii Stepanov notifications@github.com wrote:

@ajgodfrey https://github.com/ajgodfrey

Did you follow https://github.com/bitcoin/bitcoin/blob/master/doc/build-windows.md#building-for-64-bit-windows :

PATH=$(echo "$PATH" | sed -e 's/:/mnt.*//g') sudo bash -c "echo 0 > /proc/sys/fs/binfmt_misc/status" make -C depends HOST=x86_64-w64-mingw32 ...

?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bitcoin/bitcoin/issues/21332#issuecomment-789266600, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOMWNRPTCI7ZJAOFC4OQNCLTBVREFANCNFSM4YONCLAQ .

I will try running Ubuntu as a VM using VM Player for Windows and see if I get the same issue.

On Wed, Mar 3, 2021 at 9:46 AM Andrew Godfrey andrewgodf@gmail.com wrote:

I did, thanks!

On Wed, Mar 3, 2021 at 9:29 AM Hennadii Stepanov notifications@github.com wrote:

@ajgodfrey https://github.com/ajgodfrey

Did you follow https://github.com/bitcoin/bitcoin/blob/master/doc/build-windows.md#building-for-64-bit-windows :

PATH=$(echo "$PATH" | sed -e 's/:/mnt.*//g') sudo bash -c "echo 0 > /proc/sys/fs/binfmt_misc/status" make -C depends HOST=x86_64-w64-mingw32 ...

?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bitcoin/bitcoin/issues/21332#issuecomment-789266600, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOMWNRPTCI7ZJAOFC4OQNCLTBVREFANCNFSM4YONCLAQ .

**** @hebasto This bug can be closed. I went back through the instructions and found that I had made a mistake with the following: Set the default mingw32 g++ compiler option to posix. I selected the default option (0) by mistake. Thanks for your help.