On 4/23/19 9:47 PM, Gary E. Miller via devel wrote:
And that is how cruft grows...
I only disabled them at the time of my test push because I didn't
understand what they were. With that understanding I can now remove them
entirely.
--
/"In the end; what separates a Man, from a Slave?
Yo Ian!
On Tue, 23 Apr 2019 21:33:50 -0500
Ian Bruene via devel wrote:
> The hack worked.
Cool.
> On 4/23/19 9:31 PM, Hal Murray via devel wrote:
> > There is at least one other place where the test routines have a
> > routine to keep the linker happy, but I can't think of what it is.
>
>
The hack worked.
On 4/23/19 9:31 PM, Hal Murray via devel wrote:
There is at least one other place where the test routines have a routine to
keep the linker happy, but I can't think of what it is.
When it was mentioned I remembered seeing that in the nts.c tests.
Ironically I had to
Ian said:
> In trying to write tests for nts_client.c I have run into a problem I do not
> know how to solve, as it involved much of the structure of the codebase as
> well as the build system.
> Some of the code in nts_client.c calls the dns_take* series of functions.
> These functions are
Yo Ian!
On Tue, 23 Apr 2019 19:26:17 -0500
Ian Bruene via devel wrote:
> In trying to write tests for nts_client.c I have run into a problem I
> do not know how to solve, as it involved much of the structure of the
> codebase as well as the build system.
It happens.
> I have tried to move
In trying to write tests for nts_client.c I have run into a problem I do
not know how to solve, as it involved much of the structure of the
codebase as well as the build system.
Some of the code in nts_client.c calls the dns_take* series of
functions. These functions are defined in
