[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev Re: dev17 problem (still)
From: |
dickey |
Subject: |
Re: lynx-dev Re: dev17 problem (still) |
Date: |
Fri, 19 Feb 1999 07:36:13 -0500 (EST) |
>
> On Thu, 18 Feb 1999 address@hidden wrote:
>
> > > How would I check to see if that warning is "meaningful" (ie, what the
> > > heck *is* inet_addr and what is it used for)?
> > It's a function that came unstuck with Klaus' recent change - I made a
> > test to pick up that or a couple of alternatives. But it works on the
> > machines I've tested.
>
> Hmm, I didn't do anything that would change whether inet_addr is used
> or not, afaik. Could it be an indirect effect from including resolv.h,
> which I thing was done to make h_errno known? (Not needed here on linux
> with glibc anyway, h_errno is defined in netdb.h.)
yes - now that I'm looking again, I see that I meant to, but did not
put an include for <sys/types.h> in the AC_TRY_LINK macros in CF_INET_ADDR.
That will make some systems not find inet_addr.
> Klaus
--
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey
- Re: lynx-dev Re: dev17 problem (still), dickey, 1999/02/18
- Re: lynx-dev Re: dev17 problem (still), dickey, 1999/02/19
- Re: lynx-dev Re: dev17 problem (still),
dickey <=
- Re: lynx-dev Re: dev17 problem (still), dickey, 1999/02/19
- Re: lynx-dev Re: dev17 problem (still), Henry Nelson, 1999/02/23
- Re: lynx-dev Re: dev17 problem (still), dickey, 1999/02/23
- Re: lynx-dev Re: dev17 problem (still), Henry Nelson, 1999/02/23