On Tue, Nov 8, 2016 at 3:05 PM, Jakob Bohm wrote:
> On 08/11/2016 14:44, Kim Gräsman wrote:
>>
>> On Tue, Nov 8, 2016 at 2:24 PM, Michael Wojcik
>> wrote:
>>>
>>> My advice, frankly, is to study the OpenSSL build process until you
>>> understand it. We've had
>>> issues in the past with some Wind
On 08/11/2016 14:44, Kim Gräsman wrote:
On Tue, Nov 8, 2016 at 2:24 PM, Michael Wojcik
wrote:
My advice, frankly, is to study the OpenSSL build process until you understand
it. We've had
issues in the past with some Windows Perl implementations (currently we use
Cygwin Perl with
a wrapper pro
On Tue, Nov 8, 2016 at 2:24 PM, Michael Wojcik
wrote:
>
> My advice, frankly, is to study the OpenSSL build process until you
> understand it. We've had
> issues in the past with some Windows Perl implementations (currently we use
> Cygwin Perl with
> a wrapper program that corrects paths)
Forg
[not quoting anything because Outlook can't quote HTML email properly]
I build OpenSSL for static linking (though using a hacked configuration, since
it's going to be linked into a DLL, and we do not want the C RTS linked
statically). I've not seen any of these problems. We build on a variety of
Hi Kim.
Thanks for the reply.
On 8 Nov 2016 11:59 a.m., "Kim Gräsman" wrote:
>
> On Tue, Nov 8, 2016 at 6:26 AM, Ajay Garg wrote:
> >
> > Is compiling on windows always such a pain? :(
> > On Linux, it compiled perfectly the first time itself.
>
> It's worked well for me in a similar environmen
On Tue, Nov 8, 2016 at 6:26 AM, Ajay Garg wrote:
>
> Is compiling on windows always such a pain? :(
> On Linux, it compiled perfectly the first time itself.
It's worked well for me in a similar environment. I use DLL builds,
though, so `ntdll.mak` instead of `nt.mak`.
One thing that looks suspic
I tried configuring with no-asm, and then re-compiled.
Now, I get stuck at
*#error: MDC2 is disabled*
If I then *also* add no-mdc2, I get stuck at *cannot open input file
'out32\ssleay32.lib*'
Is compiling on windows always such a pain? :(
On Linux, it compiled perfectly the first time itself.
O
Oops.. sorry.
OpenSSL-version is 1.0.2d, and nasm-version is 2.12.02.
On Mon, Nov 7, 2016 at 9:31 PM, Jeremy Farrell
wrote:
> What version of OpenSSL? What version of nasm (nasm -v)? People are more
> likely to be able to help if you provide such basic information.
>
> Regards,
>
What version of OpenSSL? What version of nasm (nasm -v)? People are more
likely to be able to help if you provide such basic information.
Regards,
jjf
On 07/11/2016 11:42, Ajay Garg wrote:
Oops... pardon me.
The e) step was not done.
The errors came right after ste
perl Configure VC-WIN32 no-asm
Regards,Ishan
From: Ajay Garg
To: openssl-users@openssl.org
Sent: Monday, 7 November 2016 5:12 PM
Subject: Re: [openssl-users] Problem in compiling OpenSSL on Windows-7-32-bit
Oops... pardon me.
The e) step was not done.The errors came right after ste
Oops... pardon me.
The e) step was not done.
The errors came right after step d)
On 7 Nov 2016 3:36 p.m., "Ajay Garg" wrote:
> Hi All.
>
> Following are the steps I followed :
>
>
> ###
> a)
> Downloaded nasm.exe from
11 matches
Mail list logo
