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!
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!
FS#22903 - [mingw32-gcc] dlls installed to wrong location
Attached to Project:
Community Packages
Opened by Sven-Hendrik Haase (Svenstaro) - Tuesday, 15 February 2011, 18:48 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 15 February 2011, 20:56 GMT
Opened by Sven-Hendrik Haase (Svenstaro) - Tuesday, 15 February 2011, 18:48 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 15 February 2011, 20:56 GMT
|
DetailsThe dlls of the mingw32-gcc and mingw32-runtime packages should be installed to /usr/i486-mignw32/bin instead of /usr/i486-mignw32/lib. The reasoning is that they are required at runtime and they are not actually linked against like a .so or .a. Instead, people link against their .dll.a and the .dll needs to be available at runtime.
Windows expects them to be in the same directory as the main executable when run. I propose they should install to bin/ instead. Looking at the AUR, many packages prefer that location and autotools also targets that directory for dlls when cross-compiling. |
This task depends upon