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

Re: [PATCH] Single Character Compile nit on Win32

From: Kirby C. Bohling <kbohling_at_birddog.com>
Date: 2002-06-06 18:17:13 CEST

Kirby C. Bohling wrote:

[ snip ]

>>
>>
>> gcc 2.95 will generate warnings about the use of "long long" with
>> these options, and "long long" occurs in apr.h. There is a danger that
>> these warnings will swap anything useful. If we detect gcc 3.0 or
>> greater we could use -std=c99 -pedantic without this problem.
>>
>
> From RH7.2 man gcc
>
> -Wlong-long Warn if long long type is used. This is default. To
> inhibit the warning messages, use flag `-Wno-long-long'. Flags
> `-W-long-long' and `-Wno-long-long' are taken into account only when
> flag `-pedantic' is used.
>
> So how about -ansi -pedantic -Wno-long-long if that exists for the
> 2.95 compiler (I know RH72 uses the goofy 2.96, but I'd be surprised if
> it isn't there in the 2.95 that supports long longs)? I don't have a
> 2.95 compiler handy to test with, sorry if I'm all wrong on this one...
>
> Kirby
>

Actually this works on the gcc that shipped with 2.91, so I bet it works
with gcc 2.95.X

foo.c
int main( int argc, const char* argv[] )
{
     long long foo;

     return 0;
}

[kirby@dev kirby]$ gcc -c -pedantic -Wlong-long foo.c
foo.c: In function `main':
foo.c:3: warning: ANSI C does not support `long long'
[kirby@dev kirby]$ gcc -c -pedantic -Wno-long-long foo.c
[kirby@dev kirby]$ vim foo.c

>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 6 18:22:43 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.