Don't remove it just yet, I will email someone about it.
On Thu, Jan 31, 2019 at 11:42 AM Eric S. Raymond via devel
wrote:
> Hal Murray via devel :
> > Or does anybody know if that path has been tested? If so, when?
> >
> > In case you don't recognize the term, it's when you get with
> --enable
How hard would it be to implement, and what does it buy us?
--
Mark Atwood
http://about.me/markatwood
+1-206-604-2198
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
This looks like namespace pollution of some kind -- perhaps one of
NetBSD's standard C headers defining a bswap64 macro that conflicts
with my definition. Can you send me what aes_siv.c looks like on your
system after preprocessing?
I'm not going to support CMake 2, but CentOS has CMake 3 availabl
Has anybody else tried the latest changes on FreeBSD?
$ find /usr/ -name libaes*
/usr/local/lib/libaes_siv.so.1.0.0
/usr/local/lib/libaes_siv.so.1
/usr/local/lib/libaes_siv.so
/usr/local/lib/libaes_siv.a
$
['/usr/bin/clang', 'test.c.1.o', '-o/home/murray/ntpsec/raw/build/.conf_check_4
be
1ba75
dfoxfra...@gmail.com said:
> I think what you did will probably work if you delete your CMakeCache and try
> again
Thanks. That is the hint I needed. I was scp-ing stuff from my main system
to others giving them a bogus cache.
-
It doesn't build on NetBSD. Do you recognize the erro
On Thu, Feb 14, 2019 at 9:15 PM Hal Murray via devel wrote:
> How do I tell it that I don't want the doc?
> (I don't have a2x on that system.)
You shouldn't have to tell it anything. All the manpage
target-generation directives are wrapped in if(A2X). If a2x isn't
found, those targets won't be
How do I tell it that I don't want the doc?
(I don't have a2x on that system.)
How do I get it to use my compiler?
my compiler is at /usr/lib/ccache/gcc
(not lib64)
cmake says
The CMAKE_C_COMPILER:
/usr/lib64/ccache/cc
is not a full path to an existing compiler tool.
Tell CMake whe
On 2/13/19 5:23 PM, Gary E. Miller via devel wrote:
> Domain names can not start with digits.
This has been superseded in several RFCs, including for example:
https://tools.ietf.org/html/rfc3696#section-2
via:
https://serverfault.com/questions/638260/is-it-valid-for-a-hostname-to-start-with-a-dig
On 2/13/19 11:44 AM, Achim Gratz via devel wrote:
> Richard Laager via devel writes:
>> FWIW, I don't enable seccomp in the Debian package. It seems like a lot
>> of risk of breakage. We have an Apparmor policy, from Novell/SUSE by way
>> of Ubuntu for the ntp (NTP Classic) package.
>
> Just a wor
Daniel Franke :
> Release tags match v.., so just check the tag list for
> the most recent v1.y.z. Don't automatically go to 2.anything since releases
> are semantically versioned and that would indicate backward-incompatibility.
That's going to be a pain to implement and debug in the CI context.
On Thu, Feb 14, 2019, 2:24 PM Eric S. Raymond via devel Daniel Franke :
> > You probably don't want to auto-pull the latest HEAD every time it gets
> an
> > update; only releases get the full battery of QA. Note I'll probably be
> > stamping a release this weekend since the last release from two y
Release tags match v.., so just check the tag list for
the most recent v1.y.z. Don't automatically go to 2.anything since releases
are semantically versioned and that would indicate backward-incompatibility.
On Thu, Feb 14, 2019, 17:24 Eric S. Raymond Daniel Franke :
> > You probably don't want t
Daniel Franke :
> You probably don't want to auto-pull the latest HEAD every time it gets an
> update; only releases get the full battery of QA. Note I'll probably be
> stamping a release this weekend since the last release from two years ago
> has a build issue with more recent OpenSSL versions.
You probably don't want to auto-pull the latest HEAD every time it gets an
update; only releases get the full battery of QA. Note I'll probably be
stamping a release this weekend since the last release from two years ago
has a build issue with more recent OpenSSL versions.
On Thu, Feb 14, 2019, 17
Hal Murray :
> Did you fix the CI checks?
>
> Is anybody working on fixing libeas_siv to build on NetBSD? Until that is
> fixed, we won't build on NetBSD.
Yikes! I forgot about the CI - I almost never have to modify it.
Matt Selsky maintains that YAML file. I've pinged him on IRC. We';ll
fig
> I've added a mandatory waf check for the libaes_siv library.
Thanks.
Did you fix the CI checks?
Is anybody working on fixing libeas_siv to build on NetBSD? Until that is
fixed, we won't build on NetBSD.
--
These are my opinions. I hate spam.
I've added a mandatory waf check for the libaes_siv library.
The requirement for it has been document it in INSTALL for some time;
it's required for the NTS Support we're developing.
We didn't source-include it because Daniel wants his cmake build to
keep control of the compilation environment for
Hal Murray via devel :
> Are we interested in client certificates? If so, why?
>
> struct ntsconfig_t has:
> /* Configuration data for an NTS server or client instance */
> char *ca; /* site default */
> char *cert; /* site default */
>
> I assume that c
Eric S. Raymond via devel :
> Hal Murray via devel :
> > It's linking ntsd which we aren't interested in so I commented it out.
>
> I should just abolish that, since you;re going to be runing key service
> from ntpd.
Have done so.
--
http://www.catb.org/~esr/";>Eric S. Raymond
M
Hal Murray via devel :
> It's linking ntsd which we aren't interested in so I commented it out.
I should just abolish that, since you;re going to be runing key service
from ntpd.
--
http://www.catb.org/~esr/";>Eric S. Raymond
My work is funded by the Internet Civil Engineering In
> [105/124] Linking hgm/main/ntpd/ntsd
It's linking ntsd which we aren't interested in so I commented it out.
I think what's going on is that I added a call to msyslog which probably
dragged in a previously unused library.
--
These are my opinions. I hate spam.
___
[105/124] Linking hgm/main/ntpd/ntsd
/usr/bin/ld: libntp/libntp.a(msyslog.c.1.o): in function `addto_syslog':
/home/murray/ntpsec/raw/hgm/main/../../libntp/msyslog.c:171: undefined
reference to `progname'
/usr/bin/ld: libntp/libntp.a(msyslog.c.1.o): in function `init_logging':
/home/murray/ntpsec/
22 matches
Mail list logo
