(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 openssl-users@openssl.org
Automated List Manager majord...@openssl.org
