[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

--Wstrict-prototypes and openssl, two great things that suck together!

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2002-07-10 03:16:16 CEST

so at some point we started adding a bunch of extra gcc warnings to
our build system (which i think is a great thing BTW, compiling with
warnings turned way the hell up is good).

unfortunately, one of them is -Wstrict-prototypes.

not that i have anything against strict prototypes, quite the
contrary, i'm all for them, but they're tripping a ton of warnings in
openssl headers which my version of neon includes.

apparently openssl has a ton of things like this:

typedef struct foo {
  int (*ssl_function_pointer)();
} FOO;

and -Wstrict-warnings appears to be quite unhappy with that empty ()
at the end. changing it to (void) fixes the problem, but i don't have
the energy to fight with openssl to get them to fix their headers, and
there's a huge installed base of screwed up openssl headers already
out there, and the way things stand it makes it completely and totally
impossible to tell if there are any real warnings in libsvn_ra_dav.

so could someone tell me where the knob is to turn these extra
warnings off, for my own sanity? looking in the likely places
(configure.in, various files in ac-helpers, etc) has turned up
nothing, and i'm starting to have that 'missing something obvious'
kind of feeling...

thanks,

-garrett

-- 
garrett rooney                    Remember, any design flaw you're 
rooneg@electricjellyfish.net      sufficiently snide about becomes  
http://electricjellyfish.net/     a feature.       -- Dan Sugalski
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 10 03:16:44 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.