according to the cURL site, “Install clearly describes how to go ahead when you want to compile and install curl on your system. ”
i have included the text of the aforementioned clear description, in the more text, due to its startling … clarity.
i found more … clarity out there than you can shake a stick at. and then i found this place and these instructions:
tar -zxvf curl-x.x.tar.gz
* * * * * * *
now this doesn’t cover the part where apache continued to give me an error message about my version being too old, or how i ran through several reconfigures including the big scary one that says USE AT OWN RISK but KISS YOUR SERVER GOODBYE FIRST, which wasn’t so bad afterall. and i finally got cURL installed.
now the only problem is the script that needs it? doesn’t work.
and this is about average, as far as … clarity:
A normal unix installation is made in three or four steps (after you’ve unpacked the source archive):
make test (optional)
You probably need to be root when doing the last command.
If you have checked out the sources from the CVS repository, read the CVS-INFO on how to proceed.
Get a full listing of all available configure options by invoking it like:
If you want to install curl in a different file hierarchy than /usr/local, you need to specify that already when running configure:
If you happen to have write permission in that directory, you can do ‘make install’ without being root. An example of this would be to make a local install in your own home directory:
The configure script always tries to find a working SSL library unless explicitly told not to. If you have OpenSSL installed in the default search path for your compiler/linker, you don’t need to do anything special. If you have OpenSSL installed in /usr/local/ssl, you can run configure like:
If you have OpenSSL installed somewhere else (for example, /opt/OpenSSL,) you can run configure like this:
If you insist on forcing a build without SSL support, even though you may have OpenSSL installed in your system, you can run configure like this:
If you have OpenSSL installed, but with the libraries in one place and the header files somewhere else, you have to set the LDFLAGS and CPPFLAGS environment variables prior to running configure. Something like this should work:
(with the Bourne shell and its clones):
CPPFLAGS=”-I/path/to/ssl/include” LDFLAGS=”-L/path/to/ssl/lib” ./configure
(with csh, tcsh and their clones):
env CPPFLAGS=”-I/path/to/ssl/include” LDFLAGS=”-L/path/to/ssl/lib” ./configure
If your SSL library was compiled with rsaref (usually for use in the United States), you may also need to set:
(as suggested by Doug Kaufman)
yes! there are more options!