Hal Murray <[email protected]>:
> [ 37/211] Compiling libntp/clockwork.c
> [ 38/211] Compiling libntp/emalloc.c
> [ 39/211] Compiling libntp/hextolfp.c
> [ 40/211] Compiling libntp/humandate.c
> [ 41/211] Compiling libntp/lib_strbuf.c
> [ 42/211] Compiling libntp/msyslog.c
> [ 43/211] Compiling libntp/ntp_calendar.c
> [ 44/211] Compiling libntp/prettydate.c
> [ 45/211] Compiling libntp/statestr.c
> [ 46/211] Compiling libntp/strl_obsd.c
> [ 47/211] Compiling libntp/systime.c
> [ 48/211] Compiling libntp/timetoa.c
> 
> [ 50/211] Compiling libntp/clockwork.c
> [ 51/211] Compiling libntp/emalloc.c
> [ 52/211] Compiling libntp/hextolfp.c
> [ 53/211] Compiling libntp/humandate.c
> [ 54/211] Compiling libntp/lib_strbuf.c
> [ 55/211] Compiling libntp/msyslog.c
> [ 56/211] Compiling libntp/ntp_calendar.c
> [ 57/211] Compiling libntp/prettydate.c
> [ 58/211] Compiling libntp/statestr.c
> [ 59/211] Compiling libntp/strl_obsd.c
> [ 60/211] Compiling libntp/systime.c
> [ 61/211] Compiling libntp/timetoa.c

That's expected.  It's a quirk of waf's; they're getting built for two
different deliverables, and could have different compilation options. 
-- 
                <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
_______________________________________________
devel mailing list
[email protected]
http://lists.ntpsec.org/mailman/listinfo/devel

Reply via email to