This is with:
sanjeev@X201wily:~/SRC/ntpsec$ git describe
NTPsec_0_9_3-244-g1159155
sanjeev@X201wily:~/SRC/ntpsec$ git branch
* master
The machine runs Ubuntu 16.10 (devel). I see similar issues on a debian
testing.
Running "./waf distclean", and then "./waf configure -j 1 " ends with:
The confi
Sanjeev Gupta :
> This is with:
> sanjeev@X201wily:~/SRC/ntpsec$ git describe
> NTPsec_0_9_3-244-g1159155
> sanjeev@X201wily:~/SRC/ntpsec$ git branch
> * master
>
> The machine runs Ubuntu 16.10 (devel). I see similar issues on a debian
> testing.
>
> Running "./waf distclean", and then "./waf c
On Sun, Jul 17, 2016 at 12:59 AM, Eric S. Raymond wrote:
> Looking at it now. Can you bisect and identify the bad commit?
Ack. Started about a week ago. I put off debugging, thinking it would be
resolved with a waf distclean
--
Sanjeev Gupta
+65 98551208 http://www.linkedin.com/in/ghan
On Sun, Jul 17, 2016 at 12:59 AM, Eric S. Raymond wrote:
> Looking at it now. Can you bisect and identify the bad commit?
I have ended up at:
sanjeev@X201wily:~/SRC/ntpsec$ git bisect good
82ffaa70e3f0cebe1cf03294d41dcaa338ca7090 was both good and bad
Pulling fresh git clone now
--
Sanjeev
On Sun, Jul 17, 2016 at 12:59 AM, Eric S. Raymond wrote:
> Looking at it now. Can you bisect and identify the bad commit?
With a clean copy, and attention to detail, I see:
sanjeev@X201wily:~/SRC/111/ntpsec$ git bisect
goodc636735228e68bbd90eef8b74a20d76fee6ffed6 is the first bad commit
commi
e...@thyrsus.com said:
> I'm in favor of cleaning up and fixing some of these order dependencies, but
> I'd rather get us to a safe and functioning state first. Accordingly,
> splitting out seccomp() implementation to do it early and keeping droproot
> late is looking better and better.
I found
Sanjeev Gupta :
> Edit: I kept reading the earlier error message as "libpcap", which I have
> installed. I have now installed libcap-dev , and the configure is golden
> again.
That was expected. The new requirement is in the INSTALL file.
--
http://www.catb.org/~esr/";>Eric S. R
