1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

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

1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

neil carter
I'm trying to install the 1.0.1j version on a Windows 2003 server (32-bit), with MS Visual Studio 6.0, nasm 2.11.05, and ActiveState perl v5.16.3.

Steps involved include running the VCVARS21.BAT script, 'perl Configure VC-WIN32 --prefix=c:\openssl-1.0.1j', 'ms\do_nasm.bat', and finally 'nmake -f ms\ntdll.mak'.  Everything looks normal/good until the last step, which ends in the following:

     .\apps\s_cb.c(803) : error C2027: use of undefined type 'in6_addr'
             .\apps\s_cb.c(803) : see declaration of 'in6_addr'
     .\apps\s_cb.c(836) : error C2027: use of undefined type 'in6_addr'
             .\apps\s_cb.c(836) : see declaration of 'in6_addr'
     .\apps\s_cb.c(884) : error C2027: use of undefined type 'in6_addr'
             .\apps\s_cb.c(884) : see declaration of 'in6_addr'
     .\apps\s_cb.c(917) : error C2027: use of undefined type 'in6_addr'
             .\apps\s_cb.c(917) : see declaration of 'in6_addr'
     NMAKE : fatal error U1077: 'cl' : return code '0x2'
     Stop.

I've not seen these errors when installing previous version of OpenSSL.  I looked into the offending code in apps\s_cb.c, but I'm not a developer.

Is this a known error for the 1.0.1j version on Windows?  Has something been modified in the IPv6 code that is causing this new error?  Has no one else had this problem?

Any help is appreciated!
Reply | Threaded
Open this post in threaded view
|

Re: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

Walter H.
On 05.11.2014 18:47, neil carter wrote:
I'm trying to install the 1.0.1j version on a Windows 2003 server (32-bit), with MS Visual Studio 6.0, nasm 2.11.05, and ActiveState perl v5.16.3.

Steps involved include running the VCVARS21.BAT script, ' perl Configure VC-WIN32 --prefix=c:\openssl-1.0.1j', 'ms\do_nasm.bat', and finally 'nmake -f ms\ntdll.mak'.  Everything looks normal/good until the last step, which ends in the following:

VCVARS21.BAT = Visual C++ 2.1?
if yes, you should throw away the old ancient compiler of the early beginning of WinNT ... as of 1994;
and get the new actual Platform SDK from Microsoft ...
     .\apps\s_cb.c(803) : error C2027: use of undefined type 'in6_addr'
             .\apps\s_cb.c(803) : see declaration of 'in6_addr'
     .\apps\s_cb.c(836) : error C2027: use of undefined type 'in6_addr'
             .\apps\s_cb.c(836) : see declaration of 'in6_addr'
     .\apps\s_cb.c(884) : error C2027: use of undefined type 'in6_addr'
             .\apps\s_cb.c(884) : see declaration of 'in6_addr'
     .\apps\s_cb.c(917) : error C2027: use of undefined type 'in6_addr'
             .\apps\s_cb.c(917) : see declaration of 'in6_addr'
     NMAKE : fatal error U1077: 'cl' : return code '0x2'
     Stop.

this seems that you include ancient SDK headers not capable of IPv6 at all ...


smime.p7s (7K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

neil carter
Sorry, typo - s/b 'VCVARS32.bat'

So are you implying that MS Visual Studio 6.0 might be the issue in that it might not have built-in code with IPv6 headers?  Haven't the IPv6 pieces of the OpenSSL code been around for a while?  I know I saw posts regarding it from several years back in the list archive.

Thanks!




On 11/5/2014 12:13 PM, Walter H. wrote:
On 05.11.2014 18:47, neil carter wrote:
I'm trying to install the 1.0.1j version on a Windows 2003 server (32-bit), with MS Visual Studio 6.0, nasm 2.11.05, and ActiveState perl v5.16.3.

Steps involved include running the VCVARS21.BAT script, ' perl Configure VC-WIN32 --prefix=c:\openssl-1.0.1j', 'ms\do_nasm.bat', and finally 'nmake -f ms\ntdll.mak'.  Everything looks normal/good until the last step, which ends in the following:

VCVARS21.BAT = Visual C++ 2.1?
if yes, you should throw away the old ancient compiler of the early beginning of WinNT ... as of 1994;
and get the new actual Platform SDK from Microsoft ...
     .\apps\s_cb.c(803) : error C2027: use of undefined type 'in6_addr'
             .\apps\s_cb.c(803) : see declaration of 'in6_addr'
     .\apps\s_cb.c(836) : error C2027: use of undefined type 'in6_addr'
             .\apps\s_cb.c(836) : see declaration of 'in6_addr'
     .\apps\s_cb.c(884) : error C2027: use of undefined type 'in6_addr'
             .\apps\s_cb.c(884) : see declaration of 'in6_addr'
     .\apps\s_cb.c(917) : error C2027: use of undefined type 'in6_addr'
             .\apps\s_cb.c(917) : see declaration of 'in6_addr'
     NMAKE : fatal error U1077: 'cl' : return code '0x2'
     Stop.

this seems that you include ancient SDK headers not capable of IPv6 at all ...


Reply | Threaded
Open this post in threaded view
|

RE: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

Scott Neugroschl-2

VS6 essentially became obsolete in 2002, with the release of Visual Studio 7 .NET.

IIRC, IPv6 was still in its infancy.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of neil carter
Sent: Wednesday, November 05, 2014 10:28 AM
To: Walter H.; [hidden email]
Subject: Re: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

 

Sorry, typo - s/b 'VCVARS32.bat'

So are you implying that MS Visual Studio 6.0 might be the issue in that it might not have built-in code with IPv6 headers?  Haven't the IPv6 pieces of the OpenSSL code been around for a while?  I know I saw posts regarding it from several years back in the list archive.

Thanks!



On 11/5/2014 12:13 PM, Walter H. wrote:

On 05.11.2014 18:47, neil carter wrote:

I'm trying to install the 1.0.1j version on a Windows 2003 server (32-bit), with MS Visual Studio 6.0, nasm 2.11.05, and ActiveState perl v5.16.3.

Steps involved include running the VCVARS21.BAT script, ' perl Configure VC-WIN32 --prefix=c:\openssl-1.0.1j', 'ms\do_nasm.bat', and finally 'nmake -f ms\ntdll.mak'.  Everything looks normal/good until the last step, which ends in the following:

 

VCVARS21.BAT = Visual C++ 2.1?
if yes, you should throw away the old ancient compiler of the early beginning of WinNT ... as of 1994;
and get the new actual Platform SDK from Microsoft ...

     .\apps\s_cb.c(803) : error C2027: use of undefined type 'in6_addr'
             .\apps\s_cb.c(803) : see declaration of 'in6_addr'
     .\apps\s_cb.c(836) : error C2027: use of undefined type 'in6_addr'
             .\apps\s_cb.c(836) : see declaration of 'in6_addr'
     .\apps\s_cb.c(884) : error C2027: use of undefined type 'in6_addr'
             .\apps\s_cb.c(884) : see declaration of 'in6_addr'
     .\apps\s_cb.c(917) : error C2027: use of undefined type 'in6_addr'
             .\apps\s_cb.c(917) : see declaration of 'in6_addr'
     NMAKE : fatal error U1077: 'cl' : return code '0x2'
     Stop.

this seems that you include ancient SDK headers not capable of IPv6 at all ...

 

Reply | Threaded
Open this post in threaded view
|

Re: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

Walter H.
In reply to this post by neil carter
On 05.11.2014 19:27, neil carter wrote:
Sorry, typo - s/b 'VCVARS32.bat'

So are you implying that MS Visual Studio 6.0 might be the issue in that it might not have built-in code with IPv6 headers?
yes, definitly

WINSOCK2.H contains this:

/*
 * Constants and structures defined by the internet system,
 * Per RFC 790, September 1981, taken from the BSD file netinet/in.h.
 */

by the way: Visual C++ is from 1998, also an old ancient compiler
we have 2014 ;-)


smime.p7s (7K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

neil carter
So then why was 1.0.1g able to compile without these errors?



On 11/5/2014 12:48 PM, Walter H. wrote:
On 05.11.2014 19:27, neil carter wrote:
Sorry, typo - s/b 'VCVARS32.bat'

So are you implying that MS Visual Studio 6.0 might be the issue in that it might not have built-in code with IPv6 headers?
yes, definitly

WINSOCK2.H contains this:

/*
 * Constants and structures defined by the internet system,
 * Per RFC 790, September 1981, taken from the BSD file netinet/in.h.
 */

by the way: Visual C++ is from 1998, also an old ancient compiler
we have 2014 ;-)


Reply | Threaded
Open this post in threaded view
|

RE: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

Scott Neugroschl-2
In reply to this post by Walter H.

RFC 790 defines IPv4, not IPv6.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Walter H.
Sent: Wednesday, November 05, 2014 10:49 AM
To: neil carter
Cc: [hidden email]
Subject: Re: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

 

On 05.11.2014 19:27, neil carter wrote:

Sorry, typo - s/b 'VCVARS32.bat'

So are you implying that MS Visual Studio 6.0 might be the issue in that it might not have built-in code with IPv6 headers?

yes, definitly

WINSOCK2.H contains this:

/*
 * Constants and structures defined by the internet system,
 * Per RFC 790, September 1981, taken from the BSD file netinet/in.h.
 */

by the way: Visual C++ is from 1998, also an old ancient compiler
we have 2014 ;-)

Reply | Threaded
Open this post in threaded view
|

Re: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

Jakob Bohm
In reply to this post by neil carter
(Lets keep this on list)

The headers that shipped with Visual Studio 6.0 did not cover the
IPv6 parts of Winsock2.They were however included in the Visual
Studio 6.0 compatible platform SDKsreleasedlater, such as the
ones from at least July 2002 to sometime in 2003 or 2004.  The
April2005 platform SDK officially had limited support for Visual
Studio 6.0, although the problemswere not that large.  Later
SDKs were even less compatible with Visual Studio 6.0.

Additionally, the inclusion of Visual J++ with Visual Studio 6.0
meant that Microsofthad to remove it from all distribution
channels due to the settlement with Sun overthe Java
incompatibilities in the Microsoft Java VM.

So if you have any need for Visual C++ 6.0 (e.g. to compile NT 4.0
compatible device drivers), then you should keep your copy safe
as you can't easily get a new one.

Conclusion:

If you are compiling with Visual C++ 6.0, then you need to add a
later platform SDK to the INCLUDE and (possibly) LIB paths in the
environment before compiling OpenSSL.  Chances are that you
probably have one of those SDKs lying around already.

On 05/11/2014 19:27, neil carter wrote:

> Sorry, typo - s/b 'VCVARS32.bat'
>
> So are you implying that MS Visual Studio 6.0 might be the issue in
> that it might not have built-in code with IPv6 headers? Haven't the
> IPv6 pieces of the OpenSSL code been around for a while?  I know I saw
> posts regarding it from several years back in the list archive.
>
> Thanks!
>
>
>
>
> On 11/5/2014 12:13 PM, Walter H. wrote:
>> On 05.11.2014 18:47, neil carter wrote:
>>> I'm trying to install the 1.0.1j version on a Windows 2003 server
>>> (32-bit), with MS Visual Studio 6.0, nasm 2.11.05, and ActiveState
>>> perl v5.16.3.
>>>
>>> Steps involved include running the VCVARS21.BAT script, ' perl
>>> Configure VC-WIN32 --prefix=c:\openssl-1.0.1j', 'ms\do_nasm.bat',
>>> and finally 'nmake -f ms\ntdll.mak'. Everything looks normal/good
>>> until the last step, which ends in the following:
>>>
>> VCVARS21.BAT = Visual C++ 2.1?
>> if yes, you should throw away the old ancient compiler of the early
>> beginning of WinNT ... as of 1994;
>> and get the new actual Platform SDK from Microsoft ...
>>>      .\apps\s_cb.c(803) : error C2027: use of undefined type 'in6_addr'
>>>              .\apps\s_cb.c(803) : see declaration of 'in6_addr'
>>>      .\apps\s_cb.c(836) : error C2027: use of undefined type 'in6_addr'
>>>              .\apps\s_cb.c(836) : see declaration of 'in6_addr'
>>>      .\apps\s_cb.c(884) : error C2027: use of undefined type 'in6_addr'
>>>              .\apps\s_cb.c(884) : see declaration of 'in6_addr'
>>>      .\apps\s_cb.c(917) : error C2027: use of undefined type 'in6_addr'
>>>              .\apps\s_cb.c(917) : see declaration of 'in6_addr'
>>>      NMAKE : fatal error U1077: 'cl' : return code '0x2'
>>>      Stop.
>>>
>> this seems that you include ancient SDK headers not capable of IPv6
>> at all ...
>>
>


--
Jakob Bohm, CIO, partner, WiseMo A/S. http://www.wisemo.com
Transformervej 29, 2860 Soborg, Denmark. direct: +45 31 13 16 10
<tel:+4531131610>
This message is only for its intended recipient, delete if misaddressed.
WiseMo - Remote Service Management for PCs, Phones and Embedded
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

Jakob Bohm-7
In reply to this post by neil carter
Maybe you forgot to run the batch file that sets the
INCLUDE and LIB environment
variables to prepend later
VC 6.0 compatible SDK headers before,
such as those in
the July 2002 Platform SDK.


The copyright message quoted by Walter H. is just that,
a
copyright message acknowledging that some of the
lines
in that file were obtained from an old BSD.
That acknowledgement is still present in the June 2014
version of winsock2.h. 
Just like the
SSLeay copyright
message in most OpenSSL files refer
to that original
SSL2/3 library by EAY and TJH.


On 05/11/2014 19:53, neil carter wrote:
So then why was 1.0.1g able to compile without these errors?



On 11/5/2014 12:48 PM, Walter H. wrote:
On 05.11.2014 19:27, neil carter wrote:
Sorry, typo - s/b 'VCVARS32.bat'

So are you implying that MS Visual Studio 6.0 might be the issue in that it might not have built-in code with IPv6 headers?
yes, definitly

WINSOCK2.H contains this:

/*
 * Constants and structures defined by the internet system,
 * Per RFC 790, September 1981, taken from the BSD file netinet/in.h.
 */

by the way: Visual C++ is from 1998, also an old ancient compiler
we have 2014 ;-)




Enjoy

Jakob
-- 
Jakob Bohm, CIO, Partner, WiseMo A/S.  http://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 
Reply | Threaded
Open this post in threaded view
|

Re: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

neil carter
Okay, so what magic script is this?  Is it available in MS VS 6.0?  Sorry, not a developer so part of what everyone is saying is beyond me.

I ran the VCVARS32.bat script.  Previously that's all I've had to do to prepare the environment for installing OpenSSL.

Again, this all worked with 1.0.1g and that also included IPv6 support, didn't it?  I'm trying to understand this.

Thanks!


On 11/5/2014 1:23 PM, Jakob Bohm wrote:
Maybe you forgot to run the batch file that sets the
INCLUDE and LIB environment
variables to prepend later
VC 6.0 compatible SDK headers before,
such as those in
the July 2002 Platform SDK.


The copyright message quoted by Walter H. is just that,
a
copyright message acknowledging that some of the
lines
in that file were obtained from an old BSD.
That acknowledgement is still present in the June 2014
version of winsock2.h. 
Just like the
SSLeay copyright
message in most OpenSSL files refer
to that original
SSL2/3 library by EAY and TJH.


On 05/11/2014 19:53, neil carter wrote:
So then why was 1.0.1g able to compile without these errors?



On 11/5/2014 12:48 PM, Walter H. wrote:
On 05.11.2014 19:27, neil carter wrote:
Sorry, typo - s/b 'VCVARS32.bat'

So are you implying that MS Visual Studio 6.0 might be the issue in that it might not have built-in code with IPv6 headers?
yes, definitly

WINSOCK2.H contains this:

/*
 * Constants and structures defined by the internet system,
 * Per RFC 790, September 1981, taken from the BSD file netinet/in.h.
 */

by the way: Visual C++ is from 1998, also an old ancient compiler
we have 2014 ;-)




Enjoy

Jakob
-- 
Jakob Bohm, CIO, Partner, WiseMo A/S.  http://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 

Reply | Threaded
Open this post in threaded view
|

RE: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

Salz, Rich
> Again, this all worked with 1.0.1g and that also included IPv6 support, didn't it?  I'm trying to understand this.

No it didn't.  Or perhaps more accurately: openssl code has not changed in regards to ipv4/ipv6


--  
Principal Security Engineer, Akamai Technologies
IM: [hidden email] Twitter: RichSalz
:��I"Ϯ��r�m���� (���Z+�K�+����1���x ��h���[�z�(���Z+� ��f�y������f���h��)z{,���
Reply | Threaded
Open this post in threaded view
|

Re: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

neil carter
Let me re-phrase this.  The 1.0.1g version of OpenSSL compiled without errors in this same environment, using these same commands.


On 11/5/2014 2:25 PM, Salz, Rich wrote:
Again, this all worked with 1.0.1g and that also included IPv6 support, didn't it?  I'm trying to understand this.
No it didn't.  Or perhaps more accurately: openssl code has not changed in regards to ipv4/ipv6


--  
Principal Security Engineer, Akamai Technologies
IM: [hidden email] Twitter: RichSalz
:��I"Ϯ��r�m����(���Z+�K�+����1���x��h���[�z�(���Z+���f�y������f���h��)z{,��

Reply | Threaded
Open this post in threaded view
|

RE: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

Salz, Rich

Are you absolutely positive that you did not enable ipv6 or fail to disable ipv6, like ./config no-ipv6 ?

 

-- 

Principal Security Engineer, Akamai Technologies

IM: [hidden email] Twitter: RichSalz

Reply | Threaded
Open this post in threaded view
|

Re: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

neil carter
I was unaware that option existed until you mentioned it.



On 11/5/2014 2:32 PM, Salz, Rich wrote:

Are you absolutely positive that you did not enable ipv6 or fail to disable ipv6, like ./config no-ipv6 ?

 

-- 

Principal Security Engineer, Akamai Technologies

IM: [hidden email] Twitter: RichSalz


Reply | Threaded
Open this post in threaded view
|

Re: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

neil carter
In reply to this post by Salz, Rich
I just ran the commands again, adding the no-ipv6 to the 'perl Configure' line and received the exact same errors.


On 11/5/2014 2:32 PM, Salz, Rich wrote:

Are you absolutely positive that you did not enable ipv6 or fail to disable ipv6, like ./config no-ipv6 ?

 

-- 

Principal Security Engineer, Akamai Technologies

IM: [hidden email] Twitter: RichSalz


Reply | Threaded
Open this post in threaded view
|

Re: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

Dr. Stephen Henson
On Wed, Nov 05, 2014, neil carter wrote:

> I just ran the commands again, adding the no-ipv6 to the 'perl
> Configure' line and received the exact same errors.
>

OpenSSL tries to autodetect IPv6 support at compile time. Sometimes due to
broken or incomplete headers it gets this wrong. You can override the default
with -DOPENSSL_USE_IPV6=0 to force it not to use IPv6. You need to pass this
to Configure.

Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

neil carter
That worked!!  Thank you!!

So, next is to remove/disable SSL2 and SSL3 from the build, my original intent.

If I simply add the no-ssl2 and no-ssl3 options to the 'perl Configure' line, it returns this:

        link /nologo /subsystem:console /opt:ref /debug /dll /out:out32dll\libeay32.dll /def:ms/LIBEAY32.def @C:\DOCUME~
1\ncarter\LOCALS~1\Temp\1\nma04028.
   Creating library out32dll\libeay32.lib and object out32dll\libeay32.exp
        IF EXIST out32dll\libeay32.dll.manifest mt -nologo -manifest out32dll\libeay32.dll.manifest -outputresource:out3
2dll\libeay32.dll;2
        link /nologo /subsystem:console /opt:ref /debug /dll /out:out32dll\ssleay32.dll /def:ms/SSLEAY32.def @C:\DOCUME~
1\ncarter\LOCALS~1\Temp\1\nmb04028.
LINK : warning LNK4001: no object files specified; libraries used
LINK : warning LNK4068: /MACHINE not specified; defaulting to IX86
LINK : warning LNK4001: no object files specified; libraries used
SSLEAY32.def : error LNK2001: unresolved external symbol BIO_f_ssl
SSLEAY32.def : error LNK2001: unresolved external symbol BIO_new_buffer_ssl_connect
SSLEAY32.def : error LNK2001: unresolved external symbol BIO_new_ssl
SSLEAY32.def : error LNK2001: unresolved external symbol BIO_new_ssl_connect
SSLEAY32.def : error LNK2001: unresolved external symbol BIO_ssl_copy_session_id
SSLEAY32.def : error LNK2001: unresolved external symbol BIO_ssl_shutdown


So, I changed the options to '-DOPENSSL_USE_IPV6=0 -DOPENSSL_NO_SSL2 -DOPENSSL_NO_SSL3', but now get this:

        link /nologo /subsystem:console /opt:ref /debug /dll /out:out32dll\ssleay32.dll /def:ms/SSLEAY32.def @C:\DOCUME~
1\ncarter\LOCALS~1\Temp\1\nmb01440.
SSLEAY32.def : error LNK2001: unresolved external symbol SSLv2_client_method
SSLEAY32.def : error LNK2001: unresolved external symbol SSLv2_method
SSLEAY32.def : error LNK2001: unresolved external symbol SSLv2_server_method
out32dll\ssleay32.lib : fatal error LNK1120: 3 unresolved externals
LINK : fatal error LNK1141: failure during build of exports file
NMAKE : fatal error U1077: 'link' : return code '0x475'
Stop.


This is making me start to think there's no decent way to compile 1.0.1j on Windows while disabling SSL2 and SSL3.  I did see another post, by an Arthur Ramsey on 2014.10.16 which was similar.

Further suggestions?

A huge THANKS! to everyone's assistance thus far!!!




On 11/6/2014 6:49 AM, Dr. Stephen Henson wrote:
On Wed, Nov 05, 2014, neil carter wrote:

I just ran the commands again, adding the no-ipv6 to the 'perl
Configure' line and received the exact same errors.

OpenSSL tries to autodetect IPv6 support at compile time. Sometimes due to
broken or incomplete headers it gets this wrong. You can override the default
with -DOPENSSL_USE_IPV6=0 to force it not to use IPv6. You need to pass this
to Configure.

Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]



Reply | Threaded
Open this post in threaded view
|

Re: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

Dr. Stephen Henson
On Thu, Nov 06, 2014, neil carter wrote:

> That worked!!  Thank you!!
>
> So, next is to remove/disable SSL2 and SSL3 from the build, my
> original intent.
>
> If I simply add the no-ssl2 and no-ssl3 options to the 'perl
> Configure' line, it returns this:
>

There are a few problems with that in released versions. I'd suggest you try a
recent 1.0.1 snapshot.

Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

neil carter
Ok, so I downloaded and attempted the same build process on the openssl-1.0.1-stable-SNAP-20141106.tar.gz and get the exact same errors.

The process:
    1.    perl Configure VC-WIN32 --prefix=c:\openssl -DOPENSSL_USE_IPV6=0 -DOPENSSL_NO_SSL2 -DOPENSSL_NO_SSL3
    2.    ms\do_nasm.bat
    3.    nmake -f ms\ntdll.mak

Items (1) and (2) run clean.  Item (3) returns the following, eventually:

            link /nologo /subsystem:console /opt:ref /debug /dll /out:out32dll\ssleay32.dll /def:ms/SSLEAY32.def @C:\DOCUME~1\ncarter\LOCALS~1\Temp\1\nmb01812.
    SSLEAY32.def : error LNK2001: unresolved external symbol SSLv2_client_method
    SSLEAY32.def : error LNK2001: unresolved external symbol SSLv2_method
    SSLEAY32.def : error LNK2001: unresolved external symbol SSLv2_server_method
    out32dll\ssleay32.lib : fatal error LNK1120: 3 unresolved externals
    LINK : fatal error LNK1141: failure during build of exports file
    NMAKE : fatal error U1077: 'link' : return code '0x475'
    Stop.


I can provide the entire run and it's output if anyone wants to see it.

Thanks!!


On 11/6/2014 10:34 AM, Dr. Stephen Henson wrote:
On Thu, Nov 06, 2014, neil carter wrote:

That worked!!  Thank you!!

So, next is to remove/disable SSL2 and SSL3 from the build, my
original intent.

If I simply add the no-ssl2 and no-ssl3 options to the 'perl
Configure' line, it returns this:

There are a few problems with that in released versions. I'd suggest you try a
recent 1.0.1 snapshot.

Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]



Reply | Threaded
Open this post in threaded view
|

Re: 1.0.1j on Windows32 shows "error C2027: use of undefined type 'in6_addr'"

Dr. Stephen Henson
On Thu, Nov 06, 2014, neil carter wrote:

> Ok, so I downloaded and attempted the same build process on the
> openssl-1.0.1-stable-SNAP-20141106.tar.gz and get the exact same
> errors.
>

For that you should use no-ssl2 no-ssl3. Some of the build scripts need to
pick up those options.

Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]
12