Re: configuring --with-ssl. Oooooeeeepppppsss

All these problems can be solved be judicious use of the --prefix argument
to ./configure.  The way I've done it is:

./configure --prefix=/usr <other options>

This will put things in places where other programs can find them without
special links, etc.  Maybe /usr is not where you want to put it, but I
think ssl counts as system software and thus belongs there.  Besides,
that's where slackware puts it anyways.

On Mon, 10 Dec 2001, Myles Toomey wrote:

> this was not me originally, but I has the same problem. The Tarball
> installs in /usr/local/ssl/openssl
>
> But the only problem I had was that the make could not find the header
> files (*.h) for ssl. As soon as I cheated, it compiled and installed
> fine.
>
> On Monday, December 10, 2001, at 02:25  PM, Scott Klement wrote:
>
> >
> > Hmmm... if that's the default install location, maybe we should be
> > checking there...
> >
> > You just had to make the one symlink?   You didn't have to make another
> > symlink for /usr/local/lib?
> >
> > On Mon, 10 Dec 2001, Brian Finn wrote:
> >
> >> I had trouble compiling with SSL on Linux as well. OpenSSL seems to
> >> have put itself in /usr/local/ssl. A link from /usr/include/openssl to
> >> /usr/local/ssl/openssl seems to have done the trick. (I installed
> >> OpenSSL
> >> from the tarball.)

James Rich
james@eaerich.com