Re: [chrony-users] Chrony on DragonFly?

[Pierre Abbat <phma@xxxxxxxxxxxxx>]

On Tuesday 20 April 2010 09:52:24 Miroslav Lichvar wrote:
> On Tue, Apr 20, 2010 at 09:21:44AM -0400, Pierre Abbat wrote:
> > gcc -Wmissing-prototypes -Wall -O2 -g -DSUNOS -DHAS_STDINT_H
> > -DHAS_INTTYPES_H -DHAVE_IPV6  -c util.c
> > In file included from util.c:32:
> > sysincl.h:39:20: error: alloca.h: No such file or directory
> > In file included from sysincl.h:47,
> >                  from util.c:32:
> > /usr/include/malloc.h:2:2: warning: #warning "this file includes
> > <malloc.h> which is deprecated, use <stdlib.h> instead"
> > gmake: *** [util.o] Error 1
>
> Hm, not sure why we are including that file. Does it compile when the
> #include <alloca.h> line is removed from sysincl.h?

It compiles several files, then gives this error:

/usr/include/malloc.h:2:2: warning: #warning "this file includes <malloc.h> 
which is deprecated, use <stdlib.h> instead"
gcc -Wmissing-prototypes -Wall -O2 -g -DSUNOS -DHAS_STDINT_H -DHAS_INTTYPES_H -DHAVE_IPV6  -c 
sys_sunos.c
In file included from sys_sunos.c:33:
/usr/include/kvm.h:84: error: expected declaration specifiers or '...' 
before 'u_long'
/usr/include/kvm.h:84: error: expected declaration specifiers or '...' 
before 'size_t'
/usr/include/kvm.h:86: error: expected declaration specifiers or '...' 
before 'pid_t'
In file included from sysincl.h:47,
                 from util.h:34,
                 from sys_sunos.c:45:
/usr/include/malloc.h:2:2: warning: #warning "this file includes <malloc.h> 
which is deprecated, use <stdlib.h> instead"
sys_sunos.c: In function 'stop_adjust':
sys_sunos.c:191: warning: unused variable 'gap'
sys_sunos.c: In function 'setup_kernel':
sys_sunos.c:338: warning: unused variable 'read_back'
gmake: *** [sys_sunos.o] Error 1

Pierre

-- 
When a barnacle settles down, its brain disintegrates.
Já não percebe nada, já não percebe nada.

---
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.