Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of costin@gmail.com designates
 209.85.214.173 as permitted sender)
Received-SPF: pass (google.com: domain of costin@gmail.com designates
 10.182.89.7 as permitted sender) client-ip=10.182.89.7;
MIME-Version: 1.0
In-Reply-To: <4F452215.4020202@apache.org>
References: <4F43C691.1020009@apache.org>
	<4F43CEC8.9080200@christopherschultz.net>
	<4F43D745.7090005@apache.org>
	<CAP8-Fqmo4EwtvPjeTsQAgqqL-Wpjsfn0hiedrGtzECPSFsTPFQ@mail.gmail.com>
	<4F4403B6.50002@kippdata.de>
	<CAP8-Fqm=BweCjFOO37sAzFfLOFeOG1Y=_kkvWdOhpd51YMomBg@mail.gmail.com>
	<4F4428E3.9000704@apache.org>
	<CAP8-Fqk9yz=p6R5tJx5qTvgnEXjZAVY1X+DqFNnomVpdb9K+SA@mail.gmail.com>
	<4F449534.9080405@apache.org>
	<CAP8-FqkcyWZxkkVowUJGpD8J9AN3MbR3HiCwqZ+O9J_FpJZ6TQ@mail.gmail.com>
	<4F45141E.8000201@apache.org>
	<CAP8-FqnP2ZqbWDzxOrUK6D0tV5MfRvgLEpFBjFnih3jLseok1w@mail.gmail.com>
	<4F452215.4020202@apache.org>
Date: Wed, 22 Feb 2012 10:22:11 -0800
Message-ID: 
 <CAP8-Fqkvb899sWMMMgsijRwbB4=e=OWu5ged_gZssuRGcVr7gQ@mail.gmail.com>
Subject: Re: Release Tomcat Native 1.1.23
From: Costin Manolache <costin@gmail.com>
To: Tomcat Developers List <dev@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=f46d0447f08825678d04b9919bb0

--f46d0447f08825678d04b9919bb0
Content-Type: text/plain; charset=UTF-8

On Wed, Feb 22, 2012 at 9:12 AM, Mladen Turk <mturk@apache.org> wrote:

> On 02/22/2012 05:47 PM, Costin Manolache wrote:
>
>> On Wed, Feb 22, 2012 at 8:13 AM, Mladen Turk<mturk@apache.org>  wrote:
>>
>> One thing I would appreciate help with: I would like to have an option to
>> statically link
>> openssl and apr into the tc-native .so - I mean use openssl.a, apr.a.
>>
>>
> You mean for unixes?
> The solution would be to create stub libssl.so and libcrypto.so
> so that libtcnative don't carry their SONAME and link to system so.x...
>
> Static linkage is not a good idea I'm afraid.
>
>
>  The reason is to avoid the system libraries which will probably have the
>> wrong version.
>>
>>
> Right. Having stubs, libtcnative will always link to libssl.so which
> is usually symlink on any system.
> At runtime we can check for SSL_version and fail in case it has wrong ABI.
>
> However, not sure why you wish to do that. Many distros already provide
> tomcat-native so there's no real point for doing that, especially since
> we should not distribute unix binaries.
>

Yes, distros provide tomcat-native, apr and openssl - with the 'stable'
releases.

I'm trying to provide a way for people to build "libtcnative-2.so" so it
can be installed on
those systems along with the existing apr, openssl and libtcnative-1,
without requiring the installation of 2 versions of openssl, apr.

It seems to work for me on linux ( using cmake ) - I get a tcnative.so with
all the openssl/apr
code linked in, without dependencies to libapr.so ( no SONAME ).

So basically someone ( distros, users ) could build and deploy the new
library along with the stable ones. I don't think we can require to upgrade
the platform openssl or apr. The alternative would be to have the new
openssl/apr .so in some /usr/local/ location.

Costin


>
>
> Regards.
>
> --
> ^TM
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.**org<dev-unsubscribe@tomcat.apache.org>
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>

--f46d0447f08825678d04b9919bb0--