Unable to install OpenSSL

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Unable to install OpenSSL

Lunessia
Hello everyone,
I've been having various troubles with installing and compiling OpenSSL.
I started with 1.1.1-pre6, and my Perl client will tell me that I don't have NASM even if I have it installed (If I use VC-WIN64A) or output "If you want to report a building issue, please include the output from this command: Perl configdata.pl --dump" when I use VC-WIN64I
With 1.0.2o, Perl compiles the program, but however, I can't use Dmake to compile it, as Dmake will state:

"dmake.exe:  makefile:  line 275:  Warning: -- Found non-white space character after '[' in [@[ -n "$(THIS)" ] && $(CLEARENV) && $(MAKE) $(THIS) -e $(BUILDENV)].
dmake.exe:  makefile:  line 307:  Warning: -- Found non-white space character after '[' in [[ -z "$(FIPSCANLIB)" ] || $(CC) $(CFLAG) -Iinclude \
                -DFINGERPRINT_PREMAIN_DSO_LOAD -o $@  \
                $(FIPSLIBDIR)fips_premain.c $(FIPSLIBDIR)fipscanister.o \
                libcrypto.a $(EX_LIBS)].
dmake.exe:  makefile:  line 307:  Error: -- New group recipe begin found within group recipe."

Here are my programs:
A make implementation: Dmake from Perl
Perl 5 with core modules: ActivePerl 5.22.4.2205 with text::template installed
ANSI C Compiler: MinGW from Perl
A development environment in the form of in the form of development libraries and C header files: (I'm guessing) Visual Studio 2017 (I can't use Nmake with it for some reason)
Netwide Assembler: NASM 2.13.03
Operating system: Windows 10 x64

Some of these were found either by the .exe version or by the installer version.
Also attached is the configdata.pl dump. The makefile has not updated, so I will not include that unless asked.



 

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

Configdata.pl dump.txt (10K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Unable to install OpenSSL

Jakob Bohm-7
On 04/05/2018 02:16, Lunessia wrote:

> Hello everyone,
> I've been having various troubles with installing and compiling OpenSSL.
> I started with 1.1.1-pre6, and my Perl client will tell me that I
> don't have NASM even if I have it installed (If I use VC-WIN64A) or
> output "If you want to report a building issue, please include the
> output from this command: Perl configdata.pl <http://configdata.pm>
> --dump" when I use VC-WIN64I
> With 1.0.2o, Perl compiles the program, but however, I can't use Dmake
> to compile it, as Dmake will state:
>
Please note that VC-WIN64I is for Itanium processors (supported only
on Windows Server 2008 and 2008 R2, with some historic support on old
versions of Windows Server 2003 and Windows XP).

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
Reply | Threaded
Open this post in threaded view
|

Re: Unable to install OpenSSL

Lunessia
Thanks for the reply. If I sidestep VC-WIN64A with No-ASM, I'll get the same "If you want to report a building issue" error

On Thu, May 3, 2018 at 7:56 PM, Jakob Bohm <[hidden email]> wrote:
On 04/05/2018 02:16, Lunessia wrote:
Hello everyone,
I've been having various troubles with installing and compiling OpenSSL.
I started with 1.1.1-pre6, and my Perl client will tell me that I don't have NASM even if I have it installed (If I use VC-WIN64A) or output "If you want to report a building issue, please include the output from this command: Perl configdata.pl <http://configdata.pm> --dump" when I use VC-WIN64I
With 1.0.2o, Perl compiles the program, but however, I can't use Dmake to compile it, as Dmake will state:

Please note that VC-WIN64I is for Itanium processors (supported only
on Windows Server 2008 and 2008 R2, with some historic support on old
versions of Windows Server 2003 and Windows XP).

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


--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Reply | Threaded
Open this post in threaded view
|

Re: Unable to install OpenSSL

Jeremy Farrell
In reply to this post by Lunessia
On 04/05/2018 01:16, Lunessia wrote:
I've been having various troubles with installing and compiling OpenSSL.
I started with 1.1.1-pre6, and my Perl client will tell me that I don't have NASM even if I have it installed (If I use VC-WIN64A)

Is NASM on your execution path? If not, try with it added to the path.

or output "If you want to report a building issue, please include the output from this command: Perl configdata.pl --dump" when I use VC-WIN64I

As others have pointed out, that would configure to build for Itanium which you don't want to do - VC-WIN64A is the one you want for x64.

With 1.0.2o, Perl compiles the program, but however, I can't use Dmake to compile it, as Dmake will state:

"dmake.exe:  makefile:  line 275:  Warning: -- Found non-white space character after '[' in [@[ -n "$(THIS)" ] && $(CLEARENV) && $(MAKE) $(THIS) -e $(BUILDENV)].
dmake.exe:  makefile:  line 307:  Warning: -- Found non-white space character after '[' in [[ -z "$(FIPSCANLIB)" ] || $(CC) $(CFLAG) -Iinclude \
                -DFINGERPRINT_PREMAIN_DSO_LOAD -o $@  \
                $(FIPSLIBDIR)fips_premain.c $(FIPSLIBDIR)fipscanister.o \
                libcrypto.a $(EX_LIBS)].
dmake.exe:  makefile:  line 307:  Error: -- New group recipe begin found within group recipe."

I don't know anything about dmake, but this suggests it's not close enough to the expected version of make. I wouldn't be surprised if the VC builds effectively require nmake - they're certainly more likely to work with nmake.

Here are my programs:
A make implementation: Dmake from Perl
Perl 5 with core modules: ActivePerl 5.22.4.2205 with text::template installed
ANSI C Compiler: MinGW from Perl
A development environment in the form of in the form of development libraries and C header files: (I'm guessing) Visual Studio 2017 (I can't use Nmake with it for some reason)
Netwide Assembler: NASM 2.13.03
Operating system: Windows 10 x64

I'd find out what's stopping nmake working and fix it; then try with NASM on the path, configure with VC-WIN64A, and build with nmake.

Regards,
                          jjf
-- 
J. J. Farrell
Not speaking for Oracle.

--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Reply | Threaded
Open this post in threaded view
|

Re: Unable to install OpenSSL

Richard Levitte - VMS Whacker-2
In reply to this post by Lunessia
In message <[hidden email]> on Fri, 4 May 2018 17:55:13 -0500, Lunessia <[hidden email]> said:

jzburda> Thanks for the reply. If I sidestep VC-WIN64A with No-ASM,
jzburda> I'll get the same "If you want to report a building issue" error

You mean this?

    **********************************************************************
    ***                                                                ***
    ***   If you want to report a building issue, please include the   ***
    ***   output from this command:                                    ***
    ***                                                                ***
    ***     perl configdata.pm --dump                                  ***
    ***                                                                ***
    **********************************************************************

That's not an error, it's simply a boxed message.  It's made prominent
so no one will miss it (people do miss such message, you'd be
surprised)

Cheers,
Richard

--
Richard Levitte         [hidden email]
OpenSSL Project         http://www.openssl.org/~levitte/
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Reply | Threaded
Open this post in threaded view
|

Re: Unable to install OpenSSL

Lunessia
Jeremy Farrell> Is NASM on your execution path? If not, try with it added to the path.

I tried added NASM to both my system and user paths, and it'll still throw that error

I just realized it did make a make file. However, now I get this (this was done by sidestepping NASM)
"        rc /folibcrypto.res "libcrypto.rc"
'rc' is not recognized as an internal or external command,
operable program or batch file.
NMAKE : fatal error U1077: 'rc' : return code '0x1'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\nmake.exe"' : return code '0x2'
Stop."

On Sun, May 6, 2018 at 3:17 AM, Richard Levitte <[hidden email]> wrote:
In message <[hidden email]> on Fri, 4 May 2018 17:55:13 -0500, Lunessia <[hidden email]> said:

jzburda> Thanks for the reply. If I sidestep VC-WIN64A with No-ASM,
jzburda> I'll get the same "If you want to report a building issue" error

You mean this?

    **********************************************************************
    ***                                                                ***
    ***   If you want to report a building issue, please include the   ***
    ***   output from this command:                                    ***
    ***                                                                ***
    ***     perl configdata.pm --dump                                  ***
    ***                                                                ***
    **********************************************************************

That's not an error, it's simply a boxed message.  It's made prominent
so no one will miss it (people do miss such message, you'd be
surprised)

Cheers,
Richard

--
Richard Levitte         [hidden email]
OpenSSL Project         http://www.openssl.org/~levitte/
--
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
Reply | Threaded
Open this post in threaded view
|

Re: Unable to install OpenSSL

Lunessia
I figured out the NASM part. I added the EXE at first. Now the entire folder is targeted.

On Sun, May 6, 2018 at 10:16 PM, Lunessia <[hidden email]> wrote:
Jeremy Farrell> Is NASM on your execution path? If not, try with it added to the path.

I tried added NASM to both my system and user paths, and it'll still throw that error

I just realized it did make a make file. However, now I get this (this was done by sidestepping NASM)
"        rc /folibcrypto.res "libcrypto.rc"
'rc' is not recognized as an internal or external command,
operable program or batch file.
NMAKE : fatal error U1077: 'rc' : return code '0x1'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\nmake.exe"' : return code '0x2'
Stop."

On Sun, May 6, 2018 at 3:17 AM, Richard Levitte <[hidden email]> wrote:
In message <[hidden email]> on Fri, 4 May 2018 17:55:13 -0500, Lunessia <[hidden email]> said:

jzburda> Thanks for the reply. If I sidestep VC-WIN64A with No-ASM,
jzburda> I'll get the same "If you want to report a building issue" error

You mean this?

    **********************************************************************
    ***                                                                ***
    ***   If you want to report a building issue, please include the   ***
    ***   output from this command:                                    ***
    ***                                                                ***
    ***     perl configdata.pm --dump                                  ***
    ***                                                                ***
    **********************************************************************

That's not an error, it's simply a boxed message.  It's made prominent
so no one will miss it (people do miss such message, you'd be
surprised)

Cheers,
Richard

--
Richard Levitte         [hidden email]
OpenSSL Project         http://www.openssl.org/~levitte/
--
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
Reply | Threaded
Open this post in threaded view
|

Re: Unable to install OpenSSL

Lunessia
I also solved the RC issue by installing Windows 10 SDK tools and taking the x64 bit architecture folder that contains RC and injecting that into my system path too. I'll send a final message when the make completes, but I have a feeling this issue is closed!

On Sun, May 6, 2018 at 10:27 PM, Lunessia <[hidden email]> wrote:
I figured out the NASM part. I added the EXE at first. Now the entire folder is targeted.

On Sun, May 6, 2018 at 10:16 PM, Lunessia <[hidden email]> wrote:
Jeremy Farrell> Is NASM on your execution path? If not, try with it added to the path.

I tried added NASM to both my system and user paths, and it'll still throw that error

I just realized it did make a make file. However, now I get this (this was done by sidestepping NASM)
"        rc /folibcrypto.res "libcrypto.rc"
'rc' is not recognized as an internal or external command,
operable program or batch file.
NMAKE : fatal error U1077: 'rc' : return code '0x1'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\nmake.exe"' : return code '0x2'
Stop."

On Sun, May 6, 2018 at 3:17 AM, Richard Levitte <[hidden email]> wrote:
In message <[hidden email]> on Fri, 4 May 2018 17:55:13 -0500, Lunessia <[hidden email]> said:

jzburda> Thanks for the reply. If I sidestep VC-WIN64A with No-ASM,
jzburda> I'll get the same "If you want to report a building issue" error

You mean this?

    **********************************************************************
    ***                                                                ***
    ***   If you want to report a building issue, please include the   ***
    ***   output from this command:                                    ***
    ***                                                                ***
    ***     perl configdata.pm --dump                                  ***
    ***                                                                ***
    **********************************************************************

That's not an error, it's simply a boxed message.  It's made prominent
so no one will miss it (people do miss such message, you'd be
surprised)

Cheers,
Richard

--
Richard Levitte         [hidden email]
OpenSSL Project         http://www.openssl.org/~levitte/
--
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