checking in

[Daniel Poirot]

I am using the following in Ubuntu 14.04 LTS:

 

sudo apt-get update

sudo apt-get install bison libevent-2.0-5 libevent-dev libcap2 libcap-dev libssl1.0.0 libssl-dev libreadline6 libreadline6-dev pps-tools asciidoc

 

git clone https://github.com/ntpsec/ntpsec.git

cd ntpsec

 

/usr/bin/python2.7 /home/user/work/ntpsec/waf clean

/usr/bin/python2.7 /home/user/work/ntpsec/waf configure

/usr/bin/python2.7 /home/user/work/ntpsec/waf build check

 

 

 

From: devel [mailto:devel-bounces at ntpsec.org] On Behalf Of Joel Sherrill
Sent: Wednesday, November 25, 2015 12:18 PM
To: Mark Atwood
Cc: devel at ntpsec.org
Subject: Re: checking in

 

I have been attempting to build on CentOS/RHEL 6 and 7. I filed tickets based on experiences on each 

CentOS 6 does not have an RPM for libevent2. Thus without special work by each person building NTPsec, it won't build. AFAIK this distribution is the latest RHEL approved for use on DoD networks. I could not find a STIG for RHEL 7 so any organization which requires the DISA STIG to be applied is stuck at 6.

My CentOS 7 was missing a package and the build didn't disable the reference clocks that depended on it. Ticket filed.

The CentOS 6 issue raises some questions. Did we intend to support this OS? Long term, it highlights the problem of assuming a newer external support library is going to be part of a LTS OS distribution. I don't know if this was on the master list of supported OSes and checked when libevent2 as a dependency was discussed. I don't recall having a checklist OSes to ensure we checked all.

--joel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ntpsec.org/pipermail/devel/attachments/20151125/23318eae/attachment.html>