Charlie Fenton wrote:
> I see 3 problems:
> [1] According to config.log, the cURL configure script expects the
> header files to be in "[path]/c-ares-1.5.1/include/" but there is no
> such directory; the header files are all in "[path]/c-ares-1.5.1/".

> [2] According to config.log, the cURL configure script expects the
> built c-ares library to be at "[path]/c-ares-1.5.1/lib/libcares.a"
> but there is no "c-ares-1.5.1/lib" directory. The required library
> is at "[path]/c-ares-1.5.1/.libs//libcares.a".

> Am I missing something here or are these bugs real? We are using
> autoconf 2.61 and automake 1.10.

If you specify a path, the configure script expects an _installed_
c-ares there. I.e.
$ cd c-ares-<version>
$ ./configure --prefix=/some/path
$ make
$ make install
$ cd ../curl-<version>
$ ./configure --enable-ares=/some/path

> [3] The cURL configure script does not quote the paths and so will
> fail if the absolute path to the c-ares-1.5.1 directory contains
> spaces. I'm not sure if it will also fail if the path to the
> cURL-7.18.0 directory contains spaces.

This might be a real bug.

Michal
Received on 2008-05-13