2010/8/27 Chris Sutcliffe :
> On 26 August 2010 11:52, Chris Sutcliffe wrote:
>> On 26 August 2010 11:10, Ozkan Sezer wrote:
>>> On Thu, Aug 26, 2010 at 6:04 PM, Chris Sutcliffe wrote:
Given the assumption that PATH_SEPARATOR_CHAR *is* redundant for VMS
and HAVE_DOS_PATHS. Once we have s
On 26 August 2010 11:52, Chris Sutcliffe wrote:
> On 26 August 2010 11:10, Ozkan Sezer wrote:
>> On Thu, Aug 26, 2010 at 6:04 PM, Chris Sutcliffe wrote:
>>> Given the assumption that PATH_SEPARATOR_CHAR *is* redundant for VMS
>>> and HAVE_DOS_PATHS. Once we have something that we both think would
Does that mean I need msys to compile it? I run the script from windows
command prompt (cmd.exe)... well, that would explain POSIX-like slashes
in printed stuff. Grr, I don't want to install msys.
On 27.8.2010 16:00, Luis Lavena wrote:
> On Fri, Aug 27, 2010 at 7:04 AM, Jaroslav Šmíd wrote:
>>
On Fri, Aug 27, 2010 at 7:04 AM, Jaroslav Šmíd wrote:
> I have successfully created MSVC x64 build of OpenSSL-1.0.0a, but I need
> mingw-w64 build now. There doesn't seem to be any info in OpenSSL
> documentation, but I found it in "Projects successfully using MinGW-w64"
> list on mingw-w64 site.
I have successfully created MSVC x64 build of OpenSSL-1.0.0a, but I need
mingw-w64 build now. There doesn't seem to be any info in OpenSSL
documentation, but I found it in "Projects successfully using MinGW-w64"
list on mingw-w64 site. I have tried to configure it with
perl Configure mingw64 --
