mstorsjo
commented
3 months ago Now, I have to say that I'm building on Windows with Podman, instead of on Linux with Docker, but I suspect (actually I'm sure, it cannot be otherwise, 100% confident) the same error would be on Linux with Docker as well.
The dockerfiles do build just fine on regular Linux - see https://github.com/mstorsjo/llvm-mingw/actions/runs/9587633837 for the latest run as part of a release.
Then run
podman build -t llvm-mingw --build-arg TOOLCHAIN_ARCHS=x86_64 .
My regular builds don't use the TOOLCHAIN_ARCHS argument, so there's a chance that it does break something. But I just tested, docker build -t llvm-mingw --build-arg TOOLCHAIN_ARCHS=x86_64 . on Linux, and it built successfully.
So it does seem like it is somehow induced by something in your environment, either podman instead of Docker, or some other issue induced by building on Windows.
The problem is that
configurecannot locate the headers that have_mingw_mac.h. The headers are at/opt/llvm-mingw/generic-w64-mingw32/includeand a symlink to this directory at/opt/llvm-mingw/x86_64-w64-mingw32/include. I don't understand why it cannot see the headers though, we specify--prefix="$PREFIX/$arch-w64-mingw32"and this resolves to/opt/llvm-mingw/x86_64-w64-mingw32.
Can you show the full output from the configure script in build-mingw-w64.sh? There may be more clues there about what's going wrong further up in that output.
If you can store the failed build as an image (with regular Docker, this is usually possible by docker ps -a to find the stopped failed build, then docker commit <id> with the id of the failed build, then docker run --rm -ti <id> with the id of the new image snapshot) you can inspect the contents of mingw-w64/mingw-w64-crt/build-x86_64/config.log which may contain more info about what failed.
You can also try a change like this (untested):
diff --git a/build-mingw-w64.sh b/build-mingw-w64.sh
index 4fdfac1..83f778a 100755
--- a/build-mingw-w64.sh
+++ b/build-mingw-w64.sh
@@ -132,7 +132,7 @@ for arch in $ARCHS; do
;;
esac
FLAGS="$FLAGS --with-default-msvcrt=$DEFAULT_MSVCRT"
- ../configure --host=$arch-w64-mingw32 --prefix="$PREFIX/$arch-w64-mingw32" $FLAGS $CFGUARD_FLAGS $CRT_CONFIG_FLAGS
+ ../configure --host=$arch-w64-mingw32 --prefix="$PREFIX/$arch-w64-mingw32" $FLAGS $CFGUARD_FLAGS $CRT_CONFIG_FLAGS || { cat config.log; exit 1; }
$MAKE -j$CORES
$MAKE install
cd ..This would dump the whole config.log to stdout if it failed, but the file is huge and its hard and unwieldy to find the relevant bits from it.
pgalkin
I cannot build an image from Dockerfile, it fails on https://github.com/mstorsjo/llvm-mingw/blob/master/build-mingw-w64.sh#L135. The log is:
Now, I have to say that I'm building on Windows with Podman, instead of on Linux with Docker, but I suspect (actually I'm sure, it cannot be otherwise, 100% confident) the same error would be on Linux with Docker as well. The problem is that
configurecannot locate the headers that have_mingw_mac.h. The headers are at/opt/llvm-mingw/generic-w64-mingw32/includeand a symlink to this directory at/opt/llvm-mingw/x86_64-w64-mingw32/include. I don't understand why it cannot see the headers though, we specify--prefix="$PREFIX/$arch-w64-mingw32"and this resolves to/opt/llvm-mingw/x86_64-w64-mingw32.Another thing I should mention is that on Windows to be able to run the build on Dockerfile it's necessary to:
in
~/.gitconfig. Otherwise the shebang in shellscripts (#!/bin/sh) won't be able to find/bin/sh.Then run