[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [certi-dev] Solaris8/GCC-3.4.2; Was: Solaris10/SunStudio

From: Eric Noulard
Subject: Re: [certi-dev] Solaris8/GCC-3.4.2; Was: Solaris10/SunStudio
Date: Wed, 27 May 2009 22:17:37 +0200

2009/5/27 Martin Spott <address@hidden>:
> Eric Noulard wrote:
>> Is it really impossible to find a 64 bits long integer type on 32bits
>> machine using gcc 3.4.x ??
> If I bypass the CMake test and simply add '-DHAVE_INT64' to the
> compiler call, then the compiler doesn't complain and creates a nice
> object file - I'm even getting a nice, shared 'libHLA'.

> BUT, simply
> adding '-DHAVE_INT64' to every call (by adding it to 'CMakeLists.txt')
> doesn't lead much further:

How did you add -DHAVE_INT64 in the first place if it was not within
CMakeLists.txt ?

I think the trouble may comes from the fact CERTI is compiled with
-pedantic and -ansi which may forbids long-long usage unless one specify

However some version of gcc did not overide -ansi rules with -Wno-long-long
would you try to remove -ansi -pedantic from the main CMakeLists.txt?

> Would you like me to send you a copy of the involved int* and sys/int*
> header files ?

Yes why not,
I may find explanation with conditionnal definition of such types
in those headers.

I think I may have found a similar issue there:

If this is the case this is a gcc+solaris specific issue regarding long long....


reply via email to

[Prev in Thread] Current Thread [Next in Thread]