Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of tom.browder@gmail.com
 designates 74.125.82.177 as permitted sender)
References: 
 <CAKUrXK6LD_DuKL_LsGuVmOjQnTEdM0XDiwEOnj+B2FG4CtYQ5g@mail.gmail.com>
 <CAKQ1sVMry51XyNF9Xp=4GONcOBYxbKYEJ6kLX2=o_uog3o6POw@mail.gmail.com>
 <-4374453743531617314@unknownmsgid> <53524AA2.9040903@gmx.de>
From: Tom Browder <tom.browder@gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <53524AA2.9040903@gmx.de>
Date: Sat, 19 Apr 2014 23:13:02 +0200
Message-ID: <-9195333541648514856@unknownmsgid>
Subject: Re: Any reason why building with OpenSSL shouldn't add its lib dir to
 rpath?
To: olli hauer <ohauer@gmx.de>
Cc: "dev@httpd.apache.org" <dev@httpd.apache.org>
Content-Type: text/plain; charset=UTF-8

On Apr 19, 2014, at 12:06, olli hauer <ohauer@gmx.de> wrote:
>
> Hi Tom,
>
> with apache 2.2.x or 2.4.x ?

2.4.7 at the moment but moving to latest release where I'll try
forcing the local OpenSSL use.

I raised this issue earlier but it got no traction-- probably because
I didn't articulate the problem well enough.  IMHO the
'--with-OpenSSL=' option could benefit from the RPATH nudge suggested
by Yann (or at least suggest that move for users unwilling or unable
to remove the current system OpenSSL).

Regards,

-Tom