Re: [Mingw-w64-public] delay loading of dll

2017-02-06 Thread ltpmouse
On 2017/2/7 2:44, Hannes Domani wrote: > So dlltool did generate `__imp__dll_function`, but the linker didn't > pick it up. Meh, it is either ld's bug or dlltool's bug, but after all not mingw-w64's bug. You might want to file a bug report to binutils. -- Best regards, LH_Mouse

Re: [Mingw-w64-public] Relocation errors when linking with static libstdc++ starting with GCC 6 (64-bit only)

2017-02-06 Thread Roger Pack
> Full logs would be valuable. OK see [1] > Moreover as far as I understand, you want to build a static executable. > Please confirm that you understand the consequences on complying with > the LGPL. Since you also pass --enable-gpl, please also confirm that you > understand the consequencs on

Re: [Mingw-w64-public] delay loading of dll

2017-02-06 Thread Hannes Domani
lhmouse schrieb am 19:00 Montag, 6.Februar 2017: > Compiling app.c with `-S -masm=intel` produces the following assembly > code, with directives removed: > > _main: > pushebp > movebp, esp > andesp, -16 > call___main >

Re: [Mingw-w64-public] delay loading of dll

2017-02-06 Thread lhmouse
On 2017/2/7 0:26, Hannes Domani wrote: > Hello > > > Does delay-loading work with 32bit executables? > > In the following example it crashes for me on the dll_function() call. > I've used i686-6.3.0-release-win32-dwarf-rt_v5-rev1.7z for my tests. I compiled the program and it did crash. The

[Mingw-w64-public] delay loading of dll

2017-02-06 Thread Hannes Domani
Hello Does delay-loading work with 32bit executables? In the following example it crashes for me on the dll_function() call. I've used i686-6.3.0-release-win32-dwarf-rt_v5-rev1.7z for my tests. app.c: << __declspec(dllimport) void dll_function(