On Thu, Aug 04, 2005 at 12:09:21PM +0800, Alecs King wrote:
> Hi,
>
> I was using sparse to check the git source code and found the following
> warnings:
>
> ./commit.c:89:14: warning: undefined identifier '__LONG_MAX__'
> ./apply.c:335:50: warning: undefined identifier '__LONG_MAX__'
> ./apply.c:342:50: warning: undefined identifier '__LONG_MAX__'
>
> Thats triggered by using the macro 'ULONG_MAX'. Why does sparse frown
> at it (while gcc -E can handle it properly)?
>
> I'm using the '-DSHA1_HEADER=<openssl/sha.h>' '-Wno-transparent-union'
> options to sparse. gcc here is v3.4.4 with glibc 2.3.5-1.
Use cc=cgcc instead of cc=sparse, and it'll fill in such definitions
for you.
Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
