Re: Setting up libaes_siv

2019-02-15 Thread Hal Murray via devel
> Excellent. I just pushed the fix to HEAD. Thanks. -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel

Re: Setting up libaes_siv

2019-02-15 Thread Daniel Franke via devel
Excellent. I just pushed the fix to HEAD. On Fri, Feb 15, 2019 at 5:54 PM Hal Murray wrote: > > > dfoxfra...@gmail.com said: > > Hal, try putting > > #define _ANSI_SOURCE 1 > > #define _ISOC99_SOURCE 1 > > ... > [100%] Linking C executable demo > [100%] Built target demo > -bash-4.4$ make test >

Re: Setting up libaes_siv

2019-02-15 Thread Hal Murray via devel
dfoxfra...@gmail.com said: > Hal, try putting > #define _ANSI_SOURCE 1 > #define _ISOC99_SOURCE 1 ... [100%] Linking C executable demo [100%] Built target demo -bash-4.4$ make test Running tests... Test project /home/murray/ntpsec/libaes_siv Start 1: test 1/1 Test #1: test

Re: Setting up libaes_siv

2019-02-15 Thread Daniel Franke via devel
Hal, try putting #define _ANSI_SOURCE 1 #define _ISOC99_SOURCE 1 at the very top of aes_siv.c and let me know if that fixes the build error. Looks like the way is getting in is via via via via . But guards it with #if defined(_NETBSD_SOURCE) #include /* for quad_t, etc. */ #endif while

Re: Setting up libaes_siv

2019-02-15 Thread Daniel Franke via devel
It's exactly like I suspected: a system header is #defining bswap64 as a macro, causing a syntax error in my local definition. This is a upstream bug twice over. First, nothing should be giving you if you don't ask for it. Second, the manpage clearly states that bswap64 is a function, so it's

Re: Setting up libaes_siv

2019-02-14 Thread Daniel Franke via 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

Re: Setting up libaes_siv

2019-02-14 Thread Hal Murray via devel
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

Re: Setting up libaes_siv

2019-02-14 Thread Daniel Franke via devel
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

Setting up libaes_siv

2019-02-14 Thread Hal Murray via devel
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