You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/build-windows.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,15 +91,22 @@ Note that for WSL the Bitcoin Core source path MUST be somewhere in the default
91
91
example /usr/src/bitcoin, AND not under /mnt/d/. If this is not the case the dependency autoconf scripts will fail.
92
92
This means you cannot use a directory that is located directly on the host Windows file system to perform the build.
93
93
94
+
Additional WSL Note: WSL support for [launching Win32 applications](https://docs.microsoft.com/en-us/archive/blogs/wsl/windows-and-ubuntu-interoperability#launching-win32-applications-from-within-wsl)
95
+
results in `Autoconf` configure scripts being able to execute Windows Portable Executable files. This can cause
96
+
unexpected behaviour during the build, such as Win32 error dialogs for missing libraries. The recommended approach
97
+
is to temporarily disable WSL support for Win32 applications.
98
+
94
99
Build using:
95
100
96
101
PATH=$(echo "$PATH" | sed -e 's/:\/mnt.*//g') # strip out problematic Windows %PATH% imported var
102
+
sudo bash -c "echo 0 > /proc/sys/fs/binfmt_misc/status" # Disable WSL support for Win32 applications.
97
103
cd depends
98
104
make HOST=x86_64-w64-mingw32
99
105
cd ..
100
106
./autogen.sh # not required when building from tarball
0 commit comments