Re: [Mingw-w64-public] Successfully built cross compiler produces non-working EXE files

2024-06-06 Thread Bob via Mingw-w64-public
>You may try 2.36 for example. Binutils 2.36 segfaults while building the MinGW-w64 CRT, while 2.36.1 builds the toolchain successfully but shows the previously mentioned relocation error while compiling hello.c... Adding these flags:     -Wl,--disable-dynamicbase,--disable-high-entropy-va,--def

Re: [Mingw-w64-public] Successfully built cross compiler produces non-working EXE files

2024-06-05 Thread Bob via Mingw-w64-public
A little update on the faulty cross compiler; the problem is most certainly not in the MinGW-w64 libraries, as I swapped the libraries between the reference and faulty toolchains and the results were the same. This leaves the linker... I tried different Binutils versions and found something inte

Re: [Mingw-w64-public] Successfully built cross compiler produces non-working EXE files

2024-05-29 Thread Bob via Mingw-w64-public
Meant to reply here. https://sourceforge.net/p/mingw-w64/mailman/mingw-w64-public/thread/Nz3uczv--7-9%40tuta.io/#msg58777309 ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64

Re: [Mingw-w64-public] Successfully built cross compiler produces non-working EXE files

2024-05-29 Thread Bob via Mingw-w64-public
I did some tests to determine at which stage (compilation, assembly, linking) the faulty toolchain creates invalid output. This C program (hi.c) is what I used for testing:     int main(void) {return 0;} 1. Compilation -- `gcc -S file.c` (successful): With input hi.c, I used the faulty toolchai

[Mingw-w64-public] Successfully built cross compiler produces non-working EXE files

2024-05-28 Thread Bob via Mingw-w64-public
I have built a MinGW-w64 cross compiler on a Linux host and it successfully creates Windows executables, however said executables don't run on Windows nor Wine... A simple cross compiled 'hello-world.c' --> 'a.exe' will cause a generic "not a valid win32 application" error on Windows, while on W

Re: [Mingw-w64-public] Linking fails for GetSaveFileName when cross compiling with MinGW

2019-01-08 Thread Sailor Bob via Mingw-w64-public
, 8:36:05 PM GMT+2, Mateusz wrote: W dniu 08.01.2019 o 18:29, Sailor Bob via Mingw-w64-public pisze: > > I'm trying to compile a modified version of UniLogger on Ubuntu 18.04 using > mingw. I'm getting the following link error: > > undefined reference to '_

[Mingw-w64-public] Linking fails for GetSaveFileName when cross compiling with MinGW

2019-01-08 Thread Sailor Bob via Mingw-w64-public
I'm trying to compile a modified version of UniLogger on Ubuntu 18.04 using mingw. I'm getting the following link error: undefined reference to '_imp__GetSaveFileNameW@4' I found this post on the MinGW mailing list saying one needs to explicitly link to comdlg32 so I tried that also: i686-w6