On Fri, 14 Mar 2003, Roth, Kevin P. wrote:

> test 500... protocol FAILED
> test 501...OK
> test 502...OK
> test 503... protocol FAILED
> test 504... error FAILED
> TESTDONE: 93 tests out of 96 reported OK: 96%
> TESTFAIL: These test cases failed: 500 503 504

Strange. Can you run these tests stand-alone and see what they say:

$ cd tests
$ ./runtests.pl [num]

For 500, 503 and 504 to see if they fail every time and some more details on
the failures.

> Note - the Cygwin'ers helped me figure out the real reason builds were
> failing under Cygwin as of v7.10.x (with WinMain_at_16 error). The version of
> libtool in use (1.4.x) apparently has some issues...

Yeah, libtool sure is a fun tool! :-O See my slightly frustraded posting from
a few days ago on the libcurl list:

        http://curl.haxx.se/mail/lib-2003-03/0082.html

> Please consider upgrading the package to libtool 1.5 once it's available.
> Until then, I can build fine, but my source package become a little larger
> because of the "patch" needed to apply the reconf-ing.

I upgrade all the tools as soon as there are upgrades and there is at least
one known benefit for the curl project with it. Sometimes that backfires
though...

-- 
 Daniel Stenberg -- curl, cURL, Curl, CURL. Groks URLs.
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en