Booker C. Bense
12/1/2004 12:24:00 AM
In article <1101858511.328244.231320@f14g2000cwb.googlegroups.com>,
rcoder <rcoder@gmail.com> wrote:
>Are both versions of OpenSSL in the same prefix, (/usr by default in
>Red Hat distros) or do you have the second, non-standard package
>somewhere else? If so, I would recommend removing any LD_* or CFLAGS
>environment variables which point to the custom install; the default
>OpenSSL build provided with RHEL should be fine for building the Ruby
>extension.
_ The "custom" version is in /usr/local, the RH one in /usr. I
have no LD or CFLAGs variable set. I think the problem is that
/usr/local/lib is in /etc/ld.so.conf. So far the only thing
that's worked is to unlink /usr/local ( it's a symlink to network
shared file space. )
>
>Alternately, you should (and I do mean *should* -- I've definitely been
>bit by things in the Ruby build infrastructure that ignored sensible
>overrides in the past) be able to pass a '--with-openssl-dir=[...]'
>flag to the extconf.rb script in the ext/openssl directory of the
>source distribution to set the default path it uses. For example, if
>the OpenSSL build you need to use is in
>'/usr/local/newlibs/{include,lib}', try running the following from the
>top of the Ruby source tree:
>
>cd ext/openssl
>ruby extconf.rb --with-openssl-dir=/usr/local/newlibs
>make
>sudo make install
>
>Hope that helps,
>
_ I've tried that and every bit of autoconf foo I can think of
and the only thing that works is making /usr/local dissappear.
_ Booker C. Bense