help-cfengine
[Top][All Lists]
Advanced

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

Re: Building without ipv6 support


From: Frank Smith
Subject: Re: Building without ipv6 support
Date: Mon, 08 Mar 2004 13:30:59 -0600

Thanks, that worked.

Frank

--On Saturday, March 06, 2004 10:05:36 +0100 Mark.Burgess@iu.hio.no wrote:

> 
> In order to get here you must have the new getaddrinfo structures, I don't
> see why you would have those on such an old system. I am not sure how to
> test specifically for the new INET6 structures. You can just edit the
> configure cache and set HAVE_GETADDRINFO to false.
> 
> M
> 
> On  1 Mar, Frank Smith wrote:
>> Trying to buid cfengine-2.1.3 on an ancient Cobalt Raq2 (mips) which
>> doesn't seem to have ipv6 support.  Configure ran fine, but
>> make failed with:
>> 
>> gcc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/local/BerkeleyDB.4.0/include 
>> -I/usr/local/ssl/include   -g -O2 -Wreturn-type -Wmissing-prototypes 
>> -Wuninitialized  -g -O2 -I/usr/local/BerkeleyDB.4.0/include   -g -O2 
>> -I/usr/local/BerkeleyDB.4.0/include -c item.c
>> item.c: In function `FuzzySetMatch':
>> item.c:913: storage size of `addr1' isn't known
>> item.c:913: storage size of `addr2' isn't known
>> item.c:916: sizeof applied to an incomplete type
>> item.c:917: sizeof applied to an incomplete type
>> item.c:932: sizeof applied to an incomplete type
>> item.c:933: sizeof applied to an incomplete type
>> make[2]: *** [item.o] Error 1
>> make[2]: Leaving directory `/home/src/cfengine-2.1.3/src'
>> make[1]: *** [all] Error 2
>> make[1]: Leaving directory `/home/src/cfengine-2.1.3/src'
>> make: *** [all-recursive] Error 1
>> 
>> Line 913 of item.c is:
>> struct sockaddr_in6 addr1,addr2
>> 
>> Is there a way to disable ipv6 support in the build?
>> 
>> Thanks,
>> Frank
>> 
> 
> 
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Work: +47 22453272            Email:  Mark.Burgess@iu.hio.no
> Fax : +47 22453205            WWW  :  http://www.iu.hio.no/~mark
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~






reply via email to

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