OSSH 2.5.2p2: Why is /usr/local/ put into the include & lib p aths under Solaris?

Carson Gaspar carson at taltos.org
Wed Mar 28 18:13:48 EST 2001

--On Tuesday, March 27, 2001 11:42 PM -0500 Christopher Linn 
<celinn at mtu.edu> wrote:

> 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.

So I'm expected to hack around the fact that configure is broken and 
doesn't handle --with-openssl properly? <BZZZT> Wrong answer.


More information about the openssh-unix-dev mailing list