A package I'm preparing for submission creates a dll depending on libgcc_s_dw2-1.dll. When this dll is used and the host application exits, a crash happens. This is a known problem with libgcc_s_dw2-1.dll.
The fix is to pass -static-libgcc to the link command. This is usually done with CC="gcc -static-libgcc" configure ... Using this in a PKGBUILD has some problems: it explicitly mentions gcc and overrides whatever the user put on the `CC' variable. So what's the right method to force the build to use -static-libgcc when it links a dll? (LDFLAGS doesn't work) ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
