Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mingw-w32 build passes on W7 but fails on W10 #7712

Open
slowphil opened this issue Jan 20, 2021 · 2 comments
Open

Mingw-w32 build passes on W7 but fails on W10 #7712

slowphil opened this issue Jan 20, 2021 · 2 comments

Comments

@slowphil
Copy link

I encounter a difference in building a mingw-w32 package in nominally identical, fresh MSYS2 setups: Building passes on W7 but it fails on W10. It's not an official MSYS2/MINGW package, but I still believe it is an unexpected difference in the toolchain behaviour.

I have recorded the output of the makepkg-mingw in the log files that I attach (I removed large chunks that showed no or only insignificant differences). The first significant difference occurs at line 112 of the shortened W10 log : The linker warns about not finding libraries, although they are definitely installed (installation is identical in W7 and W10, made by script), and the build aborts shortly after.
PKGBUILD.txt
win7-short.log
win10-short.log

@jeremyd2019
Copy link
Member

I've been running into this issue a lot building packages with clang. It can be worked around by adding

export lt_cv_deplibs_check_method='pass_all'

to the start of the build() function. As for why this doesn't always break for mingw-w64 packages, that is still a mystery.

@slowphil
Copy link
Author

Yes!
That does not really answer why the toolchain behaves differently on W7 and W10, but that solves the failure on W10. Thanks for the tip.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants