cURL / Mailing Lists / curl-library / Single Mail


Re: Third party header brokenness toleration [Was: Our GnuTLS support needs polish]

From: Yang Tse <>
Date: Mon, 8 Aug 2011 18:53:30 +0200

2011/8/8 Daniel Stenberg wrote:

> I want the strictest possible checks and -Werror on code I write, but still
> I want to be able to use release versions of 3rd party libraries without
> suffering too much.

I'm not really sure we can achieve both things at the same time on the
same configure run...

In this particular case we are speaking about a quite innocent
warning, but what if it would be something more problematic such as
global symbols clashing between different third party libraries (or
even ours) because we are not using them properly?

Take for example current autobuild warning on 'Red Hat 7.2 Linux 2.4
i686 gcc 2.96 --disable-proxy':

/usr/kerberos/include/krb5.h:459: warning: declaration of
`des_random_key' shadows global declaration

It results that the autobuild is capable of running tests properly,
even with that happening. kerberos definition clashing with OpenSSL
one. But if the warning wasn't there and SSL tests failed miserably we
would have no clue at all what to search for in order to fix it.

I'm mentioning that case not because it is problematic nowadays, but
only to illustrate that without the header warnings we will miss vital
info someday

List admin:
Received on 2011-08-08