Arch Linux User Repository

Good news! Thank you!
I'll check it out soon.

UPD. Now application run fine! Thanks!

I was able to reproduce the issue and pushed a patch which fixes the problem.

Ok, good to know. I've just checked the library name and it hasn't changed between the different versions (it is and was libintl-8.dll).

I don't think a complete list of packages is required. It looks like libintl-8.dll is used by harfbuzz and glib2 (see https://martchus.dyn.f3l.de/buildservice/?#package-search-section?name=pe-x86_64%3A%3Alibintl-8.dll&mode=libdepends) and hence also indirectly loaded when starting a Qt application.

I'll see whether I can reproduce the problem when I have time.

All my package install from you repositories - mingw-w64-gettext, mingw-w64-glib2, mingw-w64-qt5-... and other for cross compiling for Windows.
Package mingw-w64-gettext version 0.22.5 too (get from my local packages cache). Application is completely rebuilt every time.
Provide a complete list of installed packages from your repository?

My repo is actually also already at version 0.24. Maybe the library name has changed so packages have to be rebuilt. However, normally my build service should catch that. So maybe there's something else wrong. I'll have a look when I'll find the time.

According to https://martchus.dyn.f3l.de/buildservice/#package-details-section?ownstuff%40x86_64%2Fmingw-w64-qt5-base Qt 5 does not even link against that library. What are you actually trying to run here?

Hello. After update to version 0.24 not run qt5 cross compiled application in windows - The Procedure DllMain Entry Point Could Not Be Located in DLL libintl-8.dll. Downgrade to version 0.22.5 solvet problem. Package setup from Martchus repositories.

The explanation on why my problem appears is explained here: https://aur.archlinux.org/packages/mingw-w64-curl#comment-965703. tl;dr, having wine installed does cause this issue, because then you can run windows binaries and configure doesn't detect that we are cross-compiling (and doesn't skip the runtime checks).

I recommend building in a clean chroot using makechrootpkg like official devs do. That's also how packages in my binary repository are built and what works for me. Note that in this environment WINE wouldn't even be installed (at least not for this package as it doesn't depend on it). Maybe you have something installed/configured in your build environment that makes the configuration script think it should/can run certain configuration tests when it actually cannot. (Having WINE installed in the build env shouldn't cause this issue on its own, though.)

Hi, right now, building this package gives me errors about undefined references to iconv_ostream_create. I found out that the configure script doesn't correctly detect iconv: it prints out "checking for working iconv... no". The reason it doesn't detect it is that after compiling the test program via i686-w64-mingw32-gcc, the script fails to run the program with these errors (from config.log):

01fc:err:module:import_dll Library libiconv-2.dll (which is needed by L"Z:\\home\\vk\\.local\\aur\\mingw-w64-gettext\\src\\gettext-0.22.5\\build-i686-w64-mingw32\\gettext-runtime\\conftest.exe") not found
01fc:err:module:loader_init Importing dlls for L"Z:\\home\\vk\\.local\\aur\\mingw-w64-gettext\\src\\gettext-0.22.5\\build-i686-w64-mingw32\\gettext-runtime\\conftest.exe" failed, status c0000135

libiconv-2.dll does exist, it's just that wine doesn't have the correct prefix. With this patch:

diff --git a/PKGBUILD b/PKGBUILD
index f62e8b3..2edf430 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -28,7 +28,7 @@ build() {
   for _arch in ${_architectures}; do
     mkdir -p build-${_arch} && pushd build-${_arch}
     export MINGW_LDFLAGS="-Wl,--enable-auto-import"
-    LIBS="-lssp" ${_arch}-configure \
+    WINEPATH=/usr/${_arch}/bin LIBS="-lssp" ${_arch}-configure \
       --disable-java \
       --disable-native-java \
       --disable-csharp \

iconv gets properly detected, and I was able to successfully build mingw-w64-gettext then. I unfortunately don't think this is how things should be done. It could be that I did something to my system and the wine prefix isn't available when building AUR packages. Any ideas?

edit: In mingw-w64-curl, there seems to be a similar problem: https://aur.archlinux.org/packages/mingw-w64-curl#comment-964645

@xantares: The comment from "patlefort" was from before the "Fix checksum" commit got pushed, it's fixed now.