#49 Fix binutils/dlltool: Creating broken import libs

v1.0 (example)
closed-fixed
nobody
5
2010-11-16
2010-10-29
morous
No

Dlltool produces broken import libs, when it is fed with object files with functions with __declspec(dllexport).

Reproduced with the attached test project with the packages mingw-w32-1.0-bin_i686-mingw_20101015.zip and mingw-w64-1.0-bin_i686-mingw_20101015.zip on 64-bit Windows7 and 32-bit Windows XP. objdump -t reveals tha lib contains symbols "DllFunc@0" and __imp__"DllFunc@0". (Yes, the symbol names contain the quotes.) Hence any attempt to use the import lib for linking any program fails because of unresolved symbols.

Workaround is to feed the dlltool with a *.def file instead of the object files. Then the symbol names do not contain the quotes.

Discussion

  • morous

    morous - 2010-10-29

    Test case

     
  • Kai Tietz

    Kai Tietz - 2010-10-30

    Issue fixed on binutils head version.

    Thanks for reporting.

    Cheers,
    Kai

     
  • Kai Tietz

    Kai Tietz - 2010-10-30
    • status: open --> closed-fixed
     
  • NightStrike

    NightStrike - 2010-11-16
    • labels: 1008204 -->
    • milestone: 747608 --> v1.0 (example)
    • summary: Creating broken import libs --> Fix binutils/dlltool: Creating broken import libs
     
  • NightStrike

    NightStrike - 2010-11-16
    • labels: --> Build 3rd party app
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks