tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <>
Subject Re: native connector tool chain
Date Mon, 21 May 2012 16:31:56 GMT
On 21/05/2012 15:35, Costin Manolache wrote:
> Sorry, haven't compiled on windows in last >10 years.
> I suspect the easiest path would be cygwin and gcc.
> If you want to use vcc - you need to find a way to generate the project
> file with the right flags. One option would be to use the CMakeLists.txt -
> you'll probably need to adjust the options and file list for windows. It
> can generate native projects for both visual studio and eclipse. The file
> is still there in main branch, the official solution is autoconf, but
> sometimes it's good to consider alternatives too.

I have Visual studio working for 95% of the build. As long as I link
OpenSSL dynamically, all is fine. It is just the static linking I am
having trouble with. This is good enough for what I need right now but
I'd like to be able to repeat the binary build process if only as
protection against the current release manager being run over by a bus.


> Costin
> On Mon, May 21, 2012 at 5:05 AM, Mark Thomas <> wrote:
>> I am trying to build the 1.1.x native connector from trunk so I can test
>> the changes I plan to make to support per socket time outs. I can build
>> using dynamic linking but not statically. What tool chain are folks
>> currently using to build the native connector binaries we currently ship?
>> My current issue relates to statically linking to OpenSSL. I get the
>> same failure with 1.0.c, 0.9.8x and 0.9.8k. I am using:
>> - Visual Studio 6 + SP6
>> - Win 2003 r2 Platform SDK
>> - OpenSSL binaries from
>> - Targeting 64-bit platform
>> I am working through the VS6 GUI and the errors I am getting are
>> variations of this:
>> ssleay32MT.lib(t1_enc.obj) : error LNK2001: unresolved external symbol
>> __GSHandlerCheck
>> Cheers,
>> Mark
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message