Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#19383 - [mingw32-binutils] Unable to link and generate DLLs using dllwrap.

Attached to Project: Community Packages
Opened by James (JRMoore) - Friday, 07 May 2010, 18:08 GMT
Last edited by Sergej Pupykin (sergej) - Saturday, 08 May 2010, 11:17 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

As the title says linking might be broken if performed with dllwrap.
For a project I'm cross-compiling after all of the objects are created the last line is similar to the following:

i486-mingw32-dllwrap -static-libgcc --def DEFFILE --driver-name c++ -Wl,--enable-stdcall-fixup OBJECTS -LLIBS_DIR -mwindows -lLIBRARIES_TO_LINK_TO -o OUTPUT_FILE

The execution of that line (with the actual files) gives the following error:

/usr/bin/ld: unrecognized option '--base-file'
/usr/bin/ld: use the --help option for usage information
collect2: ld returned 1 exit status
i486-mingw32-dllwrap: c++ exited with status 1

If the dllwrap line is changed and link is performed using g++ instead the DLL is generated as expected.

I'm using the current package mingw32-binutils 2.20.1-1
This task depends upon

Closed by  Sergej Pupykin (sergej)
Saturday, 08 May 2010, 11:17 GMT
Reason for closing:  Not a bug
Comment by James (JRMoore) - Saturday, 08 May 2010, 11:10 GMT
There are no problem in the binaries, those errors were because of the dllwrap line, the driver name should be i486-mingw32-c++ instead of c++, c++ is the one for native compilation.

Thank you anyway for everything, regards,
James Russell.

Loading...