[openssl-dev] [PATCH] Fix error in generated libeay32.def for OPENSSL_NO_ENGINE

Patch fixes LIBEAY32.def : error LNK2001: unresolved external symbol TS_CONF_set_crypto_device LIBEAY32.def : error LNK2001: unresolved external symbol TS_CONF_set_default_engine caused by always adding those functions to .def file Ensure they are added only if engine is not disabled Regards -

Re: [openssl.org #2963] Windows build bug (perl/nasm race) on OpenSSL 1.0.0c

On 01/20/2013 02:55 PM, Bruce Cran via RT wrote: We've been having regular build problems on Windows (with OpenSSL 1.0.0c, though it looks like the problem also exists in git head from 2013-01-10): sometimes nasm claims there are unresolved symbols. For example: I suspect the problem is line 1

Re: [openssl.org #1934] Enhancement request: openssl-0.9.8k Solaris CC flags

c^ via RT wrote: Hi all "./Configure solaris64-sparcv9-cc" builtin provides the CFLAGS -xtarget=ultra -xarch=v9 This is deprecated in Sun Studio12 and warns a lot. Suggest: -xtarget=ultra2 -m64 -xarch=sparc The -m64 flag doesn't work with Sun Studio 10 compilers, so it will s

Re: Win32 compile mode (static and dynamic msvcrt)

Andy Polyakov wrote: /MT option is something that cannot be used for example to link static version of openssl to the .dll, cause in that case the .dll itself would need to be statically linked against msvcrt, This is not true. You can link .obj modules originally compiled with /MT into .dll

Win32 compile mode (static and dynamic msvcrt)

Hi, With 0.9.8h+ the static version of libraries are build using /MT compiler switch while dll are build like before using /MD. Using static libraries is not possible any more cause msvcrt is linked statically. Any reason for this sudden change? /MT option is something that cannot be used for e

Re: When will tcnative-1.dll version 1.1.12 be available?

Stacy Johnson (stacjohn) wrote: Does anyone know when the new tcnative-1.dll (version 1.1.12) will be available? This does not need to be an exact date, but I need some sort of time frame (in the next week, two weeks, etc.). BTW, Tomcat Native Connector is not related to the OpenSSL (we are

Re: When will tcnative-1.dll version 1.1.12 be available?

Stacy Johnson (stacjohn) wrote: Does anyone know when the new tcnative-1.dll (version 1.1.12) will be available? This does not need to be an exact date, but I need some sort of time frame (in the next week, two weeks, etc.). Next week. Regards, Mladen ___

Re: Tomcat + HttpClient + SSL + tcnative-1.dll issues?

Stacy Johnson (stacjohn) wrote: Are there any known issues when using the Apache HttpClient to send https requests to Tomcat running with tcnative-1.dll? Perhaps different SSL stacks causing issues? Nope, it was an bug in tcnative. See: http://svn.apache.org/viewvc?rev=605571&view=rev The f

Re: [openssl.org #1627] Compilation of 0.9.8g failed on WinXP/VS2005

Steven Van Ingelgem via RT wrote: Hi, Changing the "\" into "\\" in the first parameter solves this issue. If you browse trough the archive you will see I've proposed a patch few months back that quotes all the strings in. Anyhow, here they are again. simply copy the patch to the source and

[PATCH] Windows -- fix nmake install target for cygwin and long paths

Hi, Since perl that comes with cygwin presumes unix forward slashes in the path and the nt(dll).mak requires backslashes here is the patch that allow their coexistence. Each param to $(CP) or ${MKDIR) is enclosed inside quotes, so it's properly passed as argument to the perl. Beside being able t