cURL / Mailing Lists / curl-library / Single Mail


Re: CURLE_COULDNT_RESOLVE_HOST using libcurl easy interface

From: Dan Fandrich <>
Date: Fri, 21 Dec 2012 21:18:36 +0100

On Fri, Dec 21, 2012 at 08:41:44AM -0500, Dave Galloway wrote:
> Another piece of the puzzle.
> One of our other programmers has a CentOS box with our development environment.
> He built my test program on it and it runs fine on the CentOS system.
> It segfaults on the old RH system and says the kernel is too old.
> I did some digging into the build output and there are some messages about
> needing the shared libraries from glibc at runtime for gethostbyname, gethostbyname_r, etc.
> I am guessing that the glibc that we build against is incompatible with the newer
> CentOS libraries?? Is it possible to substitute the piece of glibc for internet-type calls on
> our build box with a newer one and not break things?

glibc isn't designed for that kind of mixing-and-matching of pieces. If
name resolving is an issue, you'd probably be better off either fixing
the configuration on the remote system, or linking against another
resolver (like c-ares), which can be done statically if necessary. But,
C-ares uses some of the same configuration files (/etc/resolv.conf) so
if that's the source of the problem on that other machine, that won't

>>> Dan
List admin:
Received on 2012-12-21