-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 15.04.2014 18:41, [email protected] wrote:
> Author: Karlson2k Date: 2014-04-15 16:41:01 +0200 (Tue, 15 Apr
> 2014) New Revision: 33081
> 
> Modified: libmicrohttpd/src/microhttpd/Makefile.am Log: W32: remove
> dependency on libgcc dll with latest GCC
> 
> Modified: libmicrohttpd/src/microhttpd/Makefile.am 
> ===================================================================
>
> 
- --- libmicrohttpd/src/microhttpd/Makefile.am  2014-04-15 14:27:54 UTC
(rev 33080)
> +++ libmicrohttpd/src/microhttpd/Makefile.am  2014-04-15 14:41:01
> UTC (rev 33081) @@ -15,7 +15,7 @@ MOSTLYCLEANFILES =
> 
> if W32_SHARED_LIB_EXP -W32_MHD_LIB_LDFLAGS =
> -Wl,--output-def,$(lt_cv_objdir)/libmicrohttpd.def 
> +W32_MHD_LIB_LDFLAGS =
> -Wl,--output-def,$(lt_cv_objdir)/libmicrohttpd.def -XCClinker
> -static-libgcc noinst_DATA += $(lt_cv_objdir)/libmicrohttpd.lib
> $(lt_cv_objdir)/libmicrohttpd.def
> $(lt_cv_objdir)/libmicrohttpd.exp MOSTLYCLEANFILES +=
> $(lt_cv_objdir)/libmicrohttpd.lib $(lt_cv_objdir)/libmicrohttpd.def
> $(lt_cv_objdir)/libmicrohttpd.exp

How about making static libgcc linking optional (W32_SHARED_LIB_EXP is
true basically always for W32 builds, as all its prerequisites are
available)? And/or maybe separate static libgcc linking into separate
option.


- -- 
O< ascii ribbon - stop html email! - www.asciiribbon.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)

iQEcBAEBAgAGBQJTTUfXAAoJEOs4Jb6SI2CwSfUH/Rd599OCMsL2ej4KRvkirgLp
nFoC/S9JLXDKXIBOJMJZZp+3tAaxpMu4YMxsQUgNAFVpuv057gIy8VALFb42M51a
Gc+lhfBThPl+z2ZIyRM/tI5WpJWveEhKScJyecwDF9i0O4Mkd7OjjAtIbyMspH3l
JgUlqvLphdYolzlPAE05UtNPenisHMf/mdby0YjyVbUlh7VNLZFywcTgERw35BoZ
eZXZNO6SGrq7EENPS+LW9hsAP56EdZBUrlomChx+pzyLgDMzH1+4X2xViO9KUan/
GmLlcc8/ftNmupXtcmUx0Lo1EEod+xKJfAiqioPM9UCrC7mUK1GBoVfTTuaPvvc=
=SkXj
-----END PGP SIGNATURE-----

Reply via email to