Re: [openssl-users] Problem in compiling OpenSSL on Windows-7-32-bit

2016-11-08 Thread Kim Gräsman
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 Windows Perl implementations (currently we
>>> use Cygwin Perl with
>>> a wrapper program that corrects paths)
>>
>> Forgot to mention; I'm building with ActiveState Perl from
>> http://www.ActiveState.com.
>>
> That is the Perl most often quoted as causing problems.
>
> Try Strawberry Perl from http://strawberryperl.com/(Strawberry Perl
> is derived from vanilla Perl, hence the name).

Thanks Jakob. Funny though, it's building successfully here. The OP
hasn't reported his Perl dist yet.

I'll make a note to try with Strawberry Perl moving forward.

- Kim
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users


Re: [openssl-users] Problem in compiling OpenSSL on Windows-7-32-bit

2016-11-08 Thread Jakob Bohm

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 program that corrects paths)

Forgot to mention; I'm building with ActiveState Perl from
http://www.ActiveState.com.


That is the Perl most often quoted as causing problems.

Try Strawberry Perl from http://strawberryperl.com/(Strawberry Perl
is derived from vanilla Perl, hence the name).

Enjoy

Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S.  https://www.wisemo.com
Transformervej 29, 2860 Søborg, Denmark.  Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded

--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users


Re: [openssl-users] Problem in compiling OpenSSL on Windows-7-32-bit

2016-11-08 Thread Kim Gräsman
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)

Forgot to mention; I'm building with ActiveState Perl from
http://www.ActiveState.com.

- Kim
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users


Re: [openssl-users] Problem in compiling OpenSSL on Windows-7-32-bit

2016-11-08 Thread Michael Wojcik
[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 
Windows versions, using a number of compiler versions (because inter-version 
compatibility still eludes Microsoft); we've been doing that since the 0.9.8 
days, and now do it with each release of 1.0.2.

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), and 
as I noted above, we've had to hack the configuration process (with scripts 
that run between the OpenSSL configuration step and the actual build). The 
OpenSSL build is not trivial, and the Windows toolchain is, in a word, terrible.

I would also recommend getting nasm out of the Visual Studio tree, where it 
most definitely does not belong, and into a normal (non-spacey) path.

Michael Wojcik 
Distinguished Engineer, Micro Focus 


-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users


Re: [openssl-users] Problem in compiling OpenSSL on Windows-7-32-bit

2016-11-08 Thread Ajay Garg
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 environment. I use DLL builds,
> though, so `ntdll.mak` instead of `nt.mak`.

Unfortunately, I need to link openssl statically to our framework. So DLL
would not help, require .libs

>
> One thing that looks suspicious is this:
>
> > NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
14.0\VC\
> > N\nasm.EXE"' : return code '0x1'
>
> Have you put nasm.exe inside the Visual Studio install dir? That seems
> like an odd choice, not sure if the spaces in the path maybe confuses
> something?

I doubt, cl.exe is also inside this.

>
> You also don't mention which directory you're in when running these
> commands. I've run everything inside the openssl-1.0.2h (using a
> different version) source directory.

I am running everything from the openssl source directory itself.

Any chance I can get pre-compiled libraries for 1.0.2d, after which I can
link them statically to our framework?

Thanks in advance 

>
> - Kim
> --
> openssl-users mailing list
> To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users


Re: [openssl-users] Problem in compiling OpenSSL on Windows-7-32-bit

2016-11-07 Thread Kim Gräsman
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 suspicious is this:

> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 14.0\VC\
> N\nasm.EXE"' : return code '0x1'

Have you put nasm.exe inside the Visual Studio install dir? That seems
like an odd choice, not sure if the spaces in the path maybe confuses
something?

You also don't mention which directory you're in when running these
commands. I've run everything inside the openssl-1.0.2h (using a
different version) source directory.

- Kim
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users


Re: [openssl-users] Problem in compiling OpenSSL on Windows-7-32-bit

2016-11-07 Thread Ajay Garg
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.

On Mon, Nov 7, 2016 at 9:52 PM, Ajay Garg  wrote:

> 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,
>>jjf
>>
>> On 07/11/2016 11:42, Ajay Garg wrote:
>>
>> 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 internet, and placed it in the include-path.
>>>
>>> b)
>>> *perl Configure VC-WIN32*
>>>
>>> c)
>>>
>>>
>>> *ms\do_nasm.bat *
>>> d)
>>>
>>>
>>> * nmake -f ms\nt.mak *
>>> e)
>>> *make*
>>>
>>>
>>>
>>> *###
>>> *
>>> Compilation runs fine for some time, but then I get hundreds of
>>> IDENTICAL errors as follows ::
>>>
>>> 
>>> ###
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *tmp32\sha1-586.asm:3964: warning: `PTR' is not a NASM keyword
>>> tmp32\sha1-586.asm:3964: error: comma, colon, decorator or end of line
>>> expecte after operand tmp32\sha1-586.asm:3970: error: symbol
>>> `__sha1_block_data_order_avx' redefined tmp32\sha1-586.asm:3970: error:
>>> parser: instruction expected tmp32\sha1-586.asm:3972: error: parser:
>>> instruction expected tmp32\sha1-586.asm:3983: error: parser: instruction
>>> expected tmp32\sha1-586.asm:3985: error: parser: instruction expected
>>> tmp32\sha1-586.asm:3986: error: parser: instruction expected
>>> tmp32\sha1-586.asm:3987: warning: label alone on a line without a colon
>>> might  in error NMAKE : fatal error U1077: '"C:\Program Files\Microsoft
>>> Visual Studio 14.0\VC\ N\nasm.EXE"' : return code '0x1' Stop.*
>>>
>>>
>>> *###
>>> *
>>> Any pointers how to solve this?
>>> I will heartfully grateful.
>>>
>>> Thanks and Regards,
>>> Ajay
>>>
>>
>> --
>> J. J. Farrell
>> Not speaking for Oracle
>>
>>
>> --
>> openssl-users mailing list
>> To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
>>
>>
>
>
> --
> Regards,
> Ajay
>



-- 
Regards,
Ajay
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users


Re: [openssl-users] Problem in compiling OpenSSL on Windows-7-32-bit

2016-11-07 Thread Ajay Garg
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,
>jjf
>
> On 07/11/2016 11:42, Ajay Garg wrote:
>
> 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 internet, and placed it in the include-path.
>>
>> b)
>> *perl Configure VC-WIN32*
>>
>> c)
>>
>>
>> *ms\do_nasm.bat *
>> d)
>>
>>
>> * nmake -f ms\nt.mak *
>> e)
>> *make*
>>
>>
>>
>> *###
>> *
>> Compilation runs fine for some time, but then I get hundreds of IDENTICAL
>> errors as follows ::
>>
>> 
>> ###
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *tmp32\sha1-586.asm:3964: warning: `PTR' is not a NASM keyword
>> tmp32\sha1-586.asm:3964: error: comma, colon, decorator or end of line
>> expecte after operand tmp32\sha1-586.asm:3970: error: symbol
>> `__sha1_block_data_order_avx' redefined tmp32\sha1-586.asm:3970: error:
>> parser: instruction expected tmp32\sha1-586.asm:3972: error: parser:
>> instruction expected tmp32\sha1-586.asm:3983: error: parser: instruction
>> expected tmp32\sha1-586.asm:3985: error: parser: instruction expected
>> tmp32\sha1-586.asm:3986: error: parser: instruction expected
>> tmp32\sha1-586.asm:3987: warning: label alone on a line without a colon
>> might  in error NMAKE : fatal error U1077: '"C:\Program Files\Microsoft
>> Visual Studio 14.0\VC\ N\nasm.EXE"' : return code '0x1' Stop.*
>>
>>
>> *###
>> *
>> Any pointers how to solve this?
>> I will heartfully grateful.
>>
>> Thanks and Regards,
>> Ajay
>>
>
> --
> J. J. Farrell
> Not speaking for Oracle
>
>
> --
> openssl-users mailing list
> To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
>
>


-- 
Regards,
Ajay
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users


Re: [openssl-users] Problem in compiling OpenSSL on Windows-7-32-bit

2016-11-07 Thread Jeremy Farrell
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 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 internet, and placed it in the include-path.

b)
*perl Configure VC-WIN32*

c)
*ms\do_nasm.bat

*
d)*
nmake -f ms\nt.mak

*
e)*
*
*make*

*###


*
Compilation runs fine for some time, but then I get hundreds of
IDENTICAL errors as follows ::


###
*tmp32\sha1-586.asm:3964: warning: `PTR' is not a NASM keyword
tmp32\sha1-586.asm:3964: error: comma, colon, decorator or end of
line expecte
after operand
tmp32\sha1-586.asm:3970: error: symbol
`__sha1_block_data_order_avx' redefined
tmp32\sha1-586.asm:3970: error: parser: instruction expected
tmp32\sha1-586.asm:3972: error: parser: instruction expected
tmp32\sha1-586.asm:3983: error: parser: instruction expected
tmp32\sha1-586.asm:3985: error: parser: instruction expected
tmp32\sha1-586.asm:3986: error: parser: instruction expected
tmp32\sha1-586.asm:3987: warning: label alone on a line without a
colon might
 in error
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual
Studio 14.0\VC\
N\nasm.EXE"' : return code '0x1'
Stop.*

*###

*
Any pointers how to solve this?
I will heartfully grateful.

Thanks and Regards,
Ajay



--
J. J. Farrell
Not speaking for Oracle

-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users


Re: [openssl-users] Problem in compiling OpenSSL on Windows-7-32-bit

2016-11-07 Thread Ishan Thakur
Hi Ajay ,I am not exactly sure about this , but you can try these 2 things and 
see if it works :1. Install NASM properly , in your case its being searched at 
'"C:\Program Files\Microsoft Visual Studio 14.0\VC\N\nasm.EXE"'2.  If above 
does not works use this command :    perl Configure VC-WIN32 no-asm

Regards,Ishan


  From: Ajay Garg <ajaygargn...@gmail.com>
 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 step d)
On 7 Nov 2016 3:36 p.m., "Ajay Garg" <ajaygargn...@gmail.com> wrote:

Hi All.

Following are the steps I followed :

## ## 
###
a)
Downloaded nasm.exe from internet, and placed it in the include-path.

b)
perl Configure VC-WIN32

c)
ms\do_nasm.bat

d)
nmake -f ms\nt.mak

e)
make
## ## 
###




Compilation runs fine for some time, but then I get hundreds of IDENTICAL 
errors as follows ::

## ## 
###
tmp32\sha1-586.asm:3964: warning: `PTR' is not a NASM keyword
tmp32\sha1-586.asm:3964: error: comma, colon, decorator or end of line expecte
after operand
tmp32\sha1-586.asm:3970: error: symbol `__sha1_block_data_order_avx' redefined
tmp32\sha1-586.asm:3970: error: parser: instruction expected
tmp32\sha1-586.asm:3972: error: parser: instruction expected
tmp32\sha1-586.asm:3983: error: parser: instruction expected
tmp32\sha1-586.asm:3985: error: parser: instruction expected
tmp32\sha1-586.asm:3986: error: parser: instruction expected
tmp32\sha1-586.asm:3987: warning: label alone on a line without a colon might
 in error
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 14.0\VC\
N\nasm.EXE"' : return code '0x1'
Stop.
## ## 
###


Any pointers how to solve this?
I will heartfully grateful.



Thanks and Regards,
Ajay


-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users


   -- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users


Re: [openssl-users] Problem in compiling OpenSSL on Windows-7-32-bit

2016-11-07 Thread Ajay Garg
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 internet, and placed it in the include-path.
>
> b)
> *perl Configure VC-WIN32*
>
> c)
>
>
> *ms\do_nasm.bat*
> d)
>
>
> *nmake -f ms\nt.mak*
> e)
> *make*
>
>
>
>
>
>
> *###*
> Compilation runs fine for some time, but then I get hundreds of IDENTICAL
> errors as follows ::
>
> 
> ###
>
>
>
>
>
>
>
>
>
>
>
>
>
> *tmp32\sha1-586.asm:3964: warning: `PTR' is not a NASM
> keywordtmp32\sha1-586.asm:3964: error: comma, colon, decorator or end of
> line expecteafter operandtmp32\sha1-586.asm:3970: error: symbol
> `__sha1_block_data_order_avx' redefinedtmp32\sha1-586.asm:3970: error:
> parser: instruction expectedtmp32\sha1-586.asm:3972: error: parser:
> instruction expectedtmp32\sha1-586.asm:3983: error: parser: instruction
> expectedtmp32\sha1-586.asm:3985: error: parser: instruction
> expectedtmp32\sha1-586.asm:3986: error: parser: instruction
> expectedtmp32\sha1-586.asm:3987: warning: label alone on a line without a
> colon might in errorNMAKE : fatal error U1077: '"C:\Program Files\Microsoft
> Visual Studio 14.0\VC\N\nasm.EXE"' : return code '0x1'Stop.*
>
>
>
>
> *###*
> Any pointers how to solve this?
> I will heartfully grateful.
>
>
>
> Thanks and Regards,
> Ajay
>
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users


[openssl-users] Problem in compiling OpenSSL on Windows-7-32-bit

2016-11-07 Thread Ajay Garg
Hi All.

Following are the steps I followed :

###
a)
Downloaded nasm.exe from internet, and placed it in the include-path.

b)
*perl Configure VC-WIN32*

c)


*ms\do_nasm.bat*
d)


*nmake -f ms\nt.mak*
e)
*make*





*###*
Compilation runs fine for some time, but then I get hundreds of IDENTICAL
errors as follows ::

###













*tmp32\sha1-586.asm:3964: warning: `PTR' is not a NASM
keywordtmp32\sha1-586.asm:3964: error: comma, colon, decorator or end of
line expecteafter operandtmp32\sha1-586.asm:3970: error: symbol
`__sha1_block_data_order_avx' redefinedtmp32\sha1-586.asm:3970: error:
parser: instruction expectedtmp32\sha1-586.asm:3972: error: parser:
instruction expectedtmp32\sha1-586.asm:3983: error: parser: instruction
expectedtmp32\sha1-586.asm:3985: error: parser: instruction
expectedtmp32\sha1-586.asm:3986: error: parser: instruction
expectedtmp32\sha1-586.asm:3987: warning: label alone on a line without a
colon might in errorNMAKE : fatal error U1077: '"C:\Program Files\Microsoft
Visual Studio 14.0\VC\N\nasm.EXE"' : return code '0x1'Stop.*



*###*
Any pointers how to solve this?
I will heartfully grateful.



Thanks and Regards,
Ajay
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users