-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Konstantin Andreev on 4/27/2009 3:01 AM: > Could you explain, how the AC_USE_SYSTEM_EXTENSIONS macro works ? It > looks like the macro blindly defines all known 'extensions' symbols, > regardless of target system. Rather, it blindly defines all known extensions symbols that have not also been proven to cause problems on other platforms. > However, many applications, say, libnet, python, ImageMagick uses these > symbols in their development headers. If the application wants extensions, they probably want all available extensions. But if you have a case where defining all known extensions symbols causes a conflict that would not occur if you only defined platform-appropriate extension symbols, please post a simple test case so that we can improve the macro. > I could suppose, that if someone uses 'libnet' for development and > AC_USE_SYSTEM_EXTENSIONS as part of configuration, he gets incorrect > 'libnet' headers. How so? - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9@xxxxxxx -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkn1n2wACgkQ84KuGfSFAYBP7ACfSW8XsXCKTnqIV70g+usdPS5a VXcAnjpvsRizOSqwciR1zCHzqa62ZjTh =mCsg -----END PGP SIGNATURE----- _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
