-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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 GCC 14.2.0 build bad exe file for x86 #530
Comments
Please paste PE headers of the builds here if you have them on hand. |
Removed --image-base |
This is how I understand the problem Full log: |
Sorry, but don't you think that commit messages like "Update makefile" are harmful and do not reflect the essence. |
I make it fast in browser for testing and for you, my fault but i cant find how to edit and remove commits on web github)) P.S |
Если будешь собирать, то отпиши как что. плз |
Yes it works, I made these changes locally. According to Microsoft documentation: "For security reasons, Microsoft recommends you use the /DYNAMICBASE option instead of specifying base addresses for your executables." So it seems unnecessary to specify the base address initially. |
Operating system / операционная система
Windows 10 Pro 22H2
Running as service / Запуск программы как сервис
I run it as a regular program / Запускаю программу обычным образом
Describe the bug / Опишите ошибку программы
The linker generates a bad executable file with
i686-w64-migw32-gcc
v14.2.0, with the warning:The build was carried out from the MINGW32 (MSYS2) environment.
The file does not run: Windows 10 reports that "The application cannot be run on your PC."
Additional information / Дополнительная информация
The linker has two incompatible options
--dynamicbase
and--image-base
(see https://learn.microsoft.com/en-us/cpp/build/reference/base-base-address?view=msvc-170) which Probably on the older version (which is now in CI)mingw-w64
somehow worked.In addition, if you use
--image-base
, then for x86 it should be0x400000
, and for x640x140000000
.The text was updated successfully, but these errors were encountered: