On 03/27/2009 11:41 AM, Tsantilas Christos wrote:
> Amos Jeffries wrote:
>>..
>> It's possibly version or system dependant. I've seen this myself, it was
>> with g++, on either Solaris, CentOS, Ubuntu, or Debian, don't recall
>> exactly which machine. But I have not used any non-gcc compil
On 03/29/2009 08:22 PM, Alex Rousskov wrote:
> On 03/28/2009 06:11 AM, Tsantilas Christos wrote:
>> Hi all,
>> Currently the fs related subsystem is broken in trunk, because of the
>> known linking problems.
>>
>> I am proposing the attached patch which:
>>- modifies the configure.in script t
On 03/28/2009 06:11 AM, Tsantilas Christos wrote:
> Hi all,
> Currently the fs related subsystem is broken in trunk, because of the
> known linking problems.
>
> I am proposing the attached patch which:
>- modifies the configure.in script to define in autoconf.h file the
> HAVE_FS_UFS, HAVE_
On Mon, Mar 30, 2009 at 1:31 AM, Nagios
wrote:
> * Nagios *
>
> Notification Type: PROBLEM
>
> Service: HTTP
> Host: wiki.squid-cache.org
> Address: wiki.squid-cache.org
> State: CRITICAL
>
> Date/Time: Sun Mar 29 16:31:55 PDT 2009
>
> Additional Info:
>
> Connection refused
Sorry guys.
Hi Amos,
Some comments about "#if X" and "#ifdef X".
The gcc compiler when X is not defined, always assume that it is 0 when
appeared in an "#if". So it is safe to use the #if instead of #ifdef.
But maybe there is problem with other compilers (If I am not wrong
visual c++ is an example).
Pers
On Sun, Mar 29, 2009 at 8:04 AM, Amos Jeffries wrote:
>
> At present we have a little bit of a mess with the configure.in defined
> macros.
>
> 1) defined or undefined.
> For coding: #ifdef or #ifndef
> Combined form: #if defined(X) && defined(Y) ...
>
> 2) always defined.
> For coding
