On Tue, 4 May 2004, Justin Webb wrote:

> Nope, but it's complaining about the return types of curl_easy_strerror,
> curl_shared_strerror and curl_multi_strerror saying the first declaration in
> the header file of "unsigned char *" is different to the declaration in
> strerror.c of "const unsigned char *".

If you say so, I can't see it in my development version though.

> So I've taken a step back. Cleaned up everything and started from scratch.
> The first thing that bothers me is that I suspect it should pick up cc or
> xlc without it being specified in the environment using the CC environment
> variable, or am I off base ?

It does a best effort of finding a compiler, yes. If that effort is not good
enough, you can help it by setting the CC variable.

> If it should I'm guessing I need to look closer at my environment and not
> configure options, despite cc being in the path and available from the
> command.

Your tool set seems to provide a real challange to the configure script! ;-)

> The short question then is should I expect configure to find cc if it is
> in the path, but without defining CC= ?

Yes, that is the expected behavior. At least if cc works in a manner that
configure can understand and agree with.

-- 
     Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
      Dedicated custom curl help for hire: http://haxx.se/curl.html