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#19862 - [mingw32-gcc & mingw32-runtime] should the included *.dll files be organized in more strict way
Attached to Project:
Community Packages
Opened by Alexander Zhuk (zhuk_av) - Saturday, 19 June 2010, 16:02 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 22 June 2010, 10:09 GMT
Opened by Alexander Zhuk (zhuk_av) - Saturday, 19 June 2010, 16:02 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 22 June 2010, 10:09 GMT
|
DetailsDescription:
Theses packages include some dlls, which are needed to run programs compiled with them. Such dlls are: - /usr/i486-mingw32/bin/mingwm10.dll - /usr/bin/libstdc++-6.dll - /libgcc_s_sjlj-1.dll All these dlls are stored in different places. Moreover, one of them is in '/'. It is more convenient to store all of them in one common place. For example, in /usr/i486-mingw32/lib. An additional "plus" to such a decision is that crosscompiled win32 libraries often put their dlls into /usr/i486-mingw32/lib too. |
This task depends upon