Re: lynx-dev still problems with h_errno

[Bela Lubkin]

Tom Dickey wrote:

Bela>> I'm not familiar with the detailed operation of autoconfig, but what I 
Bela>> think is wanted here is approximately: 
Bela>>  
Bela>>   is h_errno already declared by one of the headers included by HTTCP.c? 
Bela>>      -- then do nothing 
Bela>>   otherwise, is h_errno declared if we #include <resolv.h>? 
Bela>>      -- then #include <resolv.h> in HTTCP.c 
Bela>>   otherwise, 
Bela>>      -- declare "extern int h_errno;" in HTTCP.c 

Tom> not only that: does h_errno exist in the library.

You could check for that, but I don't think it's necessary.  The code
we're trying to compile depends on a lot of other intimate details of
the BIND resolver library; it wouldn't work with any other
implementation.  And I believe BIND has had h_errno as long as the
library has existed.  The only dangerously variable part is where (and
whether) you can pick up a header file which conveniently declares it
for you, instead of having to extern it yourself.

i.e. the #ifdefs that already omit that code on other platforms, like
Windows, should exactly match the subset of systems which have h_errno.

>Bela<