echoping appears to compile and run at least on Linux, FreeBSD,
Solaris (gcc only) and Tru64. On Mac OS X, you'll probably need a
version >= 10.2. You do not have to be root to install it.

Just type "./configure", then "make", "make test" if you wish (some
tests depend on local servers and/or Internet access, interpret with
care) and then (as root if necessary), "make install".

There is also a 'make fulltest' if you want to test more things (which
may not be available on your platform).

"configure" has some options: 
--disable-http (suppress the HTTP support)
--disable-smtp (suppress the SMTP support)
--enable-icp   (add the ICP support, to monitor Web proxies like Squid)
--with-ssl[=/where/is/ssl] (add the SSL/TLS support, you will need 
         the OpenSSL library <http://www.openssl.org/>)
--disable-ttcp  (suppress the T/TCP support which is enabled only if 
         your system supports it - FreeBSD does. See 
         <http://www.kohala.com/start/ttcp.html>)

There is no option to disable IPv6. echoping now uses the new (RFC
2133) socket interface, with getnameinfo/getaddrinfo. If your system
does not support it (Mac OS X), you jave no other choices than using
echoping 4.

Standard "autoconf/configure" options are supported such as --prefix
to set the installation root directory.

If 'echoping -h' replies with a "404" error while the file really exists,
check first that you use the FQDN of the server on the command line
(this is a consequence of the HTTP 1.1 protocol, not a bug in echoping
and this will show only if the HTTP server uses "virtual hosting").

To report a bug, email Stephane Bortzmeyer
<bortz@users.sourceforge.net> (if you have an account at SourceForge,
you can use their bug reporting tool, too). If the problem is at the
"./configure" step, do not forget to send the config.log.

If echoping segfaults, please send me debugging info. To do so:
make clean
make debug
gdb ./echoping
run the-options-that-exhibits-the-problem
where
print the-variables-displayed


$Id$