On 1/21/2013 1:29 AM, Jeffrey Walton wrote:
On Sun, Jan 20, 2013 at 6:51 PM, jb-open...@wisemo.com wrote:
On 18-01-2013 20:26, Jeffrey Walton wrote:
On Fri, Jan 18, 2013 at 11:01 AM, Memmott, Lester
lester.memm...@landesk.com wrote:
All modern Versions of Microsoft's C Runtime are thread
On 18-01-2013 20:26, Jeffrey Walton wrote:
On Fri, Jan 18, 2013 at 11:01 AM, Memmott, Lester
lester.memm...@landesk.com wrote:
All modern Versions of Microsoft's C Runtime are thread safe. That occurred
around Visual Studio 6.0 (circa 2000 or so).
From
On Sun, Jan 20, 2013 at 6:51 PM, jb-open...@wisemo.com wrote:
On 18-01-2013 20:26, Jeffrey Walton wrote:
On Fri, Jan 18, 2013 at 11:01 AM, Memmott, Lester
lester.memm...@landesk.com wrote:
All modern Versions of Microsoft's C Runtime are thread safe. That
occurred around Visual Studio 6.0
I'm in the process of incorporating FIPS enabled OpenSSL into an application
when I realized that by default the FIPS module is built by dynamically linking
the C runtime, not statically linking. In my case, for Windows using Microsoft
Visual Studio it uses the /MD option, instead of /MT.
On Fri, Jan 18, 2013 at 10:21 AM, Memmott, Lester
lester.memm...@landesk.com wrote:
I'm in the process of incorporating FIPS enabled OpenSSL into an application
when I realized that by default the FIPS module is built by dynamically
linking the C runtime, not statically linking. In my case,
All modern Versions of Microsoft's C Runtime are thread safe. That occurred
around Visual Studio 6.0 (circa 2000 or so).
From http://msdn.microsoft.com/en-us/library/abx4dbyh.aspx: The
single-threaded CRT (libc.lib, libcd.lib) (formerly the /ML or /MLd
options) is no longer available. Instead,
On Fri, Jan 18, 2013 at 11:01 AM, Memmott, Lester
lester.memm...@landesk.com wrote:
All modern Versions of Microsoft's C Runtime are thread safe. That occurred
around Visual Studio 6.0 (circa 2000 or so).
From http://msdn.microsoft.com/en-us/library/abx4dbyh.aspx: The
single-threaded CRT
