Forcing use of newer version of OpenSSL

[Jerry]

On Tue, 15 Sep 2015 18:00:49 +0100, Matthew Seaman stated:

> On 09/15/15 17:33, Jerry wrote:
> > I have both OpenSSL 1.0.1l-freebsd 15 Jan 2015 {located in /usr/bin} and
> > OpenSSL 1.0.2d 9 Jul 2015 {located in /usr/local/bin} residing on my
> > system. Now, I want to use and hopefully link programs against the
> > "port", ie, newer version. If I adjust the path to use "/usr/local/bin"
> > first, some programs fail to build. I discovered this a few months ago
> > and received that bit of knowledge on this forum. I therefore changed the
> > path so "/usr/bin" goes before "/usr/local/bin". That has the effect of
> > causing the older version of OpenSSL being used.
> > 
> > Other than permanently changing the path, and then changing it back when a
> > build fails, how can I permanently fix this problem. IMHO, the newer
> > version should permanently  overwrite the older version. I don't need or
> > want to versions. Since the older version comes with the base system, I
> > am hesitant to try and remove it. In a perfect world, the base system
> > would be updated, but I guess that is not going to happen anytime soon.
> 
> For anything you want to compile from ports, just add:
> 
> WITH_OPENSSL_PORT=      yes
> 
> to /etc/make.conf (or /usr/local/etc/poudriere.d/make.conf if you're
> using poudriere)
> 
> Additionally you have to be careful of some ports that have GSSAPI
> options -- don't enable GSSAPI support from the base system, or you'll
> end up with a binary linked against two different versions of OpenSSL
> libraries.  Apart from that, the ports openssl is pretty much a drop-in
> replacement.
> 
> For stuff you're compiling yourself, outside of ports, you need to force
> your compilation to use the appropriate -I (for include files) and -L
> (for libraries) search paths when compiling C code.  How to do this is
> specific to the compilation system used by whatever code your trying to
> compile.
> 
> It's not feasible to remove openssl from base -- too much stuff in base
> needs it -- nor is it feasible to overwrite the base openssl with the
> ports version -- the ABIs have changed between the two versions.
> 
> I believe the ultimate plan is to make the base version of openssl a
> private library and require all ported software to use the ports version
> of openssl, but that is for future implementation.

I have the notation in the /etc/make.conf file. My question is how do I force
the use of the newer version of OpenSSL, other than by changing the $PATH
setting? Changing the $PATH setting causes some programs to fail to build. I
don't remember exactly what programs were involved though.

Thanks for you help.

-- 
Jerry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20150915/4fadeabc/attachment.bin>