openssh unix dev - Mar 2001 - OSSH 2.5.2p2: Why is /usr/local/ put into the include & lib p aths under Solaris?

But the main question hasn't been answered: Why is /usr/local placed before
user-specified paths? Hypothetical example: You want to link against OpenSSL
0.96 for OpenSSH, but /usr/local contains 0.95, which is needed for
something else. (Assume it comes binary only on Solaris for the sake of
argument...)

--Matt
> -----Original Message-----
> From: Damien Miller [mailto:djm at mindrot.org]
> Sent: Tuesday, March 27, 2001 7:48 PM
> To: Carson Gaspar
> Cc: openssh-unix-dev at mindrot.org
> Subject: Re: OSSH 2.5.2p2: Why is /usr/local/ put into the 
> include & lib
> paths under Solaris?
> 
> 
> On Tue, 27 Mar 2001, Carson Gaspar wrote:
> 
> > I'd like to know why /usr/local/(include|lib) is added to the
> > (include|library) path. I'd _especially_ like to know why 
> it's added before
> > user-specified library directories such as OpenSSL. If I specify
> > --with-openssl=/foo/openssl, I want to actually _use_ the version of
> > openssl in /foo/openssl, not some version that may have 
> been installed in
> > /usr/local. This really makes no sense at all, since 
> Solaris doesn't even
> > _have_ /usr/local by default.
> >
> > Attached is a patch that gets rid of this behaviour, at 
> least for solaris.
> > I suspect it's bogus on just about every platform, but I'm 
> sure it is on
> > Solaris.
> 
> Many people and packages (like most of sunfreeware) put stuff in
> /usr/local.
> 
> -d
> 
> -- 
> | Damien Miller <djm at mindrot.org> \ ``E-mail attachments are 
> the poor man's
> | http://www.mindrot.org          /   distributed 
> filesystem'' - Dan Geer
>

On Tue, Mar 27, 2001 at 07:59:50PM -0800, Lewandowsky, Matt
wrote:
> But the main question hasn't been answered: Why is /usr/local placed
before
> user-specified paths? Hypothetical example: You want to link against
OpenSSL
> 0.96 for OpenSSH, but /usr/local contains 0.95, which is needed for
> something else. (Assume it comes binary only on Solaris for the sake of
> argument...)
because it is so easy to dodge that already when you run ./configure.

if you use env insertions in the command line of ./configure, like:

	CPPFLAGS="-I/my/include/dir" \
	CFLAGS="whatever" \
	LDFLAGS="-L/my/lib/Ldir -R/my/lib/Rdir" \
		./configure
			--option-1 \
			--option-2 \
	...etc...

when you load your env like this, configure will insert those -ahead-
of /usr/local, whereas if you use the --cppflags/--cflags/--ldflags
configure options, those are placed -after- /usr/local.

cheers,

chris

-- 
Christopher Linn, <celinn at mtu.edu>    | By no means shall either the
CEC
Staff System Administrator            | or MTU be held in any way liable
  Center for Experimental Computation | for any opinions or conjecture I
    Michigan Technological University | hold to or imply to hold herein.