Laurent,

> Trouble is that I have quite a few versions of curl now on my disk. And
> maybe the cpan one is not the better one ?

As Daniel notes, WWW::Curl (previously known as Curl::easy) is *not* curl or
libcurl, but a perl interface to libcurl. You must have a correctly
configured and working version of libcurl installed on your machine before
you can install or use the perl interface.

> I think my troubles are also coming from the use of cpan Curl::easy
> module. So I will get back to there first and look what's going badly.

If you actually want to use the perl interface to libcurl, you should probably
download the installation tarball and read the README and Makefile.PL
comments, rather than relying solely on the CPAN automated install procedure
at the moment.

A fully automated install is tricky for WWW::Curl, because on many platforms
(windows at least, probably MacOS X from your description), the libraries
and header files are in varying locations, and there may or may not be a
working PATH to use to find curl-config.

Also, the 'regression tests' which the automated CPAN installer likes to run
require some external servers to be configured to test against. The "hang"
you saw (if on caused by a faulty libcurl installation), is probably caused
by one of the tests prompting for a URL to be used for testing, or by the ssl
tests (which contact a list of common websites) taking some time to complete.

(WWW::Curl 2.01 will use some TestHarness or MakeMaker routines to avoid
prompting in these circumstances)

If you do need to make any configuration changes or fixes to run on MacOS/X,
please report them back to me, or the libcurl list, or to the CPAN/Perl
bugtracker - rt.perl.org/perlbug, against the appropriate module name.

Cris

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Received on 2003-09-16