Looking for libssl32.dll: see also
  http://curl.haxx.se/mail/archive-2002-09/0064.html

OpenSSL produces only two DLLs when built: one contains the crypto code and
some support, while the second contains the SSL/TLS protocol code. The fact
that you need three(!) SSL DLLs hints at a situation where you have a
codebase using OpenSSL which is in limbo between two major OpenSSL release
series (0.9.6 and 0.9.current).

Caveat: since I don't know DataWire, it may also be that libssl32.dll is not
OpenSSL itself, but some 'wrapper' DLL around the SSL library, but you'll
find that out quick enough if DataWire doesn't use the API as provided by
OpenSSL itself.

HTH,

Ger



On Tue, Mar 18, 2008 at 9:22 AM, Rich O'Brien via RT <[EMAIL PROTECTED]> wrote:

> This issue has been resolved.
>
> We are still looking for the "libssl32.dll". It was no where to be found.
>
>
>  _____
>
> We need the following required files for DataWire development.
>
> <From OpenSSL>/libeay32.dll
> <From OpenSSL>/ssleay32.dll
> <From OpenSSL>/libssl32.dll
>
> We installed,
> ActivePerl
>
> We have VisualStudio 2005 Professional
>
> We ran
> > ms\do_ms
>
>  _____
>
> C:\Dev\DataWire\openssl-0.9.8g>ms\do_ms
>
> C:\Dev\DataWire\openssl-0.9.8g>perl util\mkfiles.pl  1>MINFO
>
> C:\Dev\DataWire\openssl-0.9.8g>perl util\mk1mf.pl no-asm VC-WIN32
> 1>ms\nt.mak
>
> C:\Dev\DataWire\openssl-0.9.8g>perl util\mk1mf.pl dll no-asm VC-WIN32
> 1>ms\ntdll.mak
>
> C:\Dev\DataWire\openssl-0.9.8g>perl util\mk1mf.pl no-asm VC-CE
>  1>ms\ce.mak
> %OSVERSION% is not defined at util/pl/VC-32.pl line 41.
> Compilation failed in require at util\mk1mf.pl line 138.
>
> C:\Dev\DataWire\openssl-0.9.8g>perl util\mk1mf.pl dll no-asm VC-CE
> 1>ms\cedll.mak
> %OSVERSION% is not defined at util/pl/VC-32.pl line 41.
> Compilation failed in require at util\mk1mf.pl line 138.
>
> C:\Dev\DataWire\openssl-0.9.8g>perl util\mkdef.pl 32 libeay
> 1>ms\libeay32.def
>
> C:\Dev\DataWire\openssl-0.9.8g>perl util\mkdef.pl 32 ssleay
> 1>ms\ssleay32.def
>
>  _____
>
>
> But we get a fatal error on our nmake call below,
>
>  _____
>
> C:\Dev\DataWire\openssl-0.9.8g>nmake -f ms\ntdll.mak
>
> Microsoft (R) Program Maintenance Utility Version 8.00.50727.762
> Copyright (C) Microsoft Corporation.  All rights reserved.
>
> Building OpenSSL
>        perl util/copy.pl .\crypto\buildinf.h tmp32dll\buildinf.h
> Copying: ./crypto/buildinf.h to tmp32dll/buildinf.h
>        cl /Fotmp32dll\uplink.obj -Iinc32 -Itmp32dll /MD /Ox /O2 /Ob2 /W3
> /WX /G
> s0 /GF /Gy /nologo -DOPENSSL_SYSNAME_WIN32 -DWIN32_LEAN_AND_MEAN
> -DL_ENDIAN
> -DDS
> O_WIN32 -D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE
> -DOPENSSL_SYSNAME
> _WINNT -DUNICODE -D_UNICODE -DOPENSSL_USE_APPLINK -I. /Fdout32dll
> -DOPENSSL_NO_C
> AMELLIA -DOPENSSL_NO_SEED -DOPENSSL_NO_RC5 -DOPENSSL_NO_MDC2
> -DOPENSSL_NO_TLSEXT
>  -DOPENSSL_NO_KRB5 -DOPENSSL_NO_DYNAMIC_ENGINE -D_WINDLL  -c ms\uplink.c
> uplink.c
> ms\uplink.c(11) : fatal error C1083: Cannot open include file: 'windows.h
> ':
> No s
> uch file or directory
> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
> 8\VC\BIN\c
> l.EXE"' : return code '0x2'
> Stop.
>  _____
>
>
> We have a windows.h resource file, but it is dated from 1998 from our
> VisualStudio 2003 install.
>
> We tried as suggested in support  "7. Why does the OpenSSL compilation
> fail
> on Win32 with VC?" but same result.
>
>  _____
>
> C:\Dev\DataWire\openssl-0.9.8g>VSVARS32.BAT
> Setting environment for using Microsoft Visual Studio 2005 x86 tools.
>
> C:\Dev\DataWire\openssl-0.9.8g>nmake -f ms\ntdll.mak
>
> Microsoft (R) Program Maintenance Utility Version 8.00.50727.762
> Copyright (C) Microsoft Corporation.  All rights reserved.
>
> Building OpenSSL
>        cl /Fotmp32dll\uplink.obj -Iinc32 -Itmp32dll /MD /Ox /O2 /Ob2 /W3
> /WX /G
> s0 /GF /Gy /nologo -DOPENSSL_SYSNAME_WIN32 -DWIN32_LEAN_AND_MEAN
> -DL_ENDIAN
> -DDS
> O_WIN32 -D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE
> -DOPENSSL_SYSNAME
> _WINNT -DUNICODE -D_UNICODE -DOPENSSL_USE_APPLINK -I. /Fdout32dll
> -DOPENSSL_NO_C
> AMELLIA -DOPENSSL_NO_SEED -DOPENSSL_NO_RC5 -DOPENSSL_NO_MDC2
> -DOPENSSL_NO_TLSEXT
>  -DOPENSSL_NO_KRB5 -DOPENSSL_NO_DYNAMIC_ENGINE -D_WINDLL  -c ms\uplink.c
> uplink.c
> ms\uplink.c(11) : fatal error C1083: Cannot open include file: 'windows.h
> ':
> No s
> uch file or directory
> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
> 8\VC\BIN\c
> l.EXE"' : return code '0x2'
> Stop.
>
>  _____
>
>
> Any suggestions?
>
> Thanks in advance.
>
> Rich O'Brien
>
> 970 W Valley Parkway, #456
> Escondido, CA 92025
> [EMAIL PROTECTED]
> (760) 291-0081 Main
> (760) 807-1590 Cell/Mobile
> (760) 291-0070 FAX
>  _____
>
> *** The information in this message may be proprietary and/or
> confidential,
> and protected from disclosure. If the reader of this message is not the
> intended recipient, or an employee or agent responsible for delivering
> this
> message to the intended recipient, you are hereby notified that any
> dissemination, distribution or copying of this communication is strictly
> prohibited. If you have received this communication in error, please
> notify
> 1stTransaction Corporation immediately by replying to this message and
> deleting it from your computer. ***
>
>
>
>  This issue has been resolved.
>
> We are still looking for the "libssl32.dll". It was no where to be found.
>
>
>  ------------------------------
>  We need the following required files for DataWire development.
>
> <From OpenSSL>/libeay32.dll
> <From OpenSSL>/ssleay32.dll
> <From OpenSSL>/libssl32.dll
>
> We installed,
> ActivePerl
>
> We have VisualStudio 2005 Professional
>
> We ran
> > ms\do_ms
>
>  ------------------------------
>  C:\Dev\DataWire\openssl-0.9.8g>ms\do_ms
>
> C:\Dev\DataWire\openssl-0.9.8g>perl util\mkfiles.pl  1>MINFO
>
> C:\Dev\DataWire\openssl-0.9.8g>perl util\mk1mf.pl no-asm VC-WIN32
> 1>ms\nt.mak
>
> C:\Dev\DataWire\openssl-0.9.8g>perl util\mk1mf.pl dll no-asm VC-WIN32
> 1>ms\ntdll.mak
>
> C:\Dev\DataWire\openssl-0.9.8g>perl util\mk1mf.pl no-asm VC-CE
> 1>ms\ce.mak
> %OSVERSION% is not defined at util/pl/VC-32.pl line 41.
> Compilation failed in require at util\mk1mf.pl line 138.
>
> C:\Dev\DataWire\openssl-0.9.8g>perl util\mk1mf.pl dll no-asm VC-CE
> 1>ms\cedll.mak
> %OSVERSION% is not defined at util/pl/VC-32.pl line 41.
> Compilation failed in require at util\mk1mf.pl line 138.
>
> C:\Dev\DataWire\openssl-0.9.8g>perl util\mkdef.pl 32 libeay
> 1>ms\libeay32.def
>
> C:\Dev\DataWire\openssl-0.9.8g>perl util\mkdef.pl 32 ssleay
> 1>ms\ssleay32.def
> ------------------------------
>
> But we get a fatal error on our nmake call below,
>
>  ------------------------------
>  C:\Dev\DataWire\openssl-0.9.8g>nmake -f ms\ntdll.mak
>
> Microsoft (R) Program Maintenance Utility Version 8.00.50727.762
> Copyright (C) Microsoft Corporation.  All rights reserved.
>
> Building OpenSSL
>         perl util/copy.pl .\crypto\buildinf.h tmp32dll\buildinf.h
> Copying: ./crypto/buildinf.h to tmp32dll/buildinf.h
>         cl /Fotmp32dll\uplink.obj -Iinc32 -Itmp32dll /MD /Ox /O2 /Ob2 /W3
> /WX /G
> s0 /GF /Gy /nologo -DOPENSSL_SYSNAME_WIN32 -DWIN32_LEAN_AND_MEAN
> -DL_ENDIAN -DDS
> O_WIN32 -D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE
> -DOPENSSL_SYSNAME
> _WINNT -DUNICODE -D_UNICODE -DOPENSSL_USE_APPLINK -I. /Fdout32dll
> -DOPENSSL_NO_C
> AMELLIA -DOPENSSL_NO_SEED -DOPENSSL_NO_RC5 -DOPENSSL_NO_MDC2
> -DOPENSSL_NO_TLSEXT
>  -DOPENSSL_NO_KRB5 -DOPENSSL_NO_DYNAMIC_ENGINE -D_WINDLL  -c ms\uplink.c
> uplink.c
> ms\uplink.c(11) : fatal error C1083: Cannot open include file: 'windows.h':
> No s
> uch file or directory
> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
> 8\VC\BIN\c
> l.EXE"' : return code '0x2'
> Stop.
>  ------------------------------
>
> We have a windows.h resource file, but it is dated from 1998 from our
> VisualStudio 2003 install.
>
> We tried as suggested in support  "*7. Why does the OpenSSL compilation
> fail on Win32 with VC*?" but same result.
>
>  ------------------------------
>  C:\Dev\DataWire\openssl-0.9.8g>VSVARS32.BAT
> Setting environment for using Microsoft Visual Studio 2005 x86 tools.
>
> C:\Dev\DataWire\openssl-0.9.8g>nmake -f ms\ntdll.mak
>
> Microsoft (R) Program Maintenance Utility Version 8.00.50727.762
> Copyright (C) Microsoft Corporation.  All rights reserved.
>
> Building OpenSSL
>         cl /Fotmp32dll\uplink.obj -Iinc32 -Itmp32dll /MD /Ox /O2 /Ob2 /W3
> /WX /G
> s0 /GF /Gy /nologo -DOPENSSL_SYSNAME_WIN32 -DWIN32_LEAN_AND_MEAN
> -DL_ENDIAN -DDS
> O_WIN32 -D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE
> -DOPENSSL_SYSNAME
> _WINNT -DUNICODE -D_UNICODE -DOPENSSL_USE_APPLINK -I. /Fdout32dll
> -DOPENSSL_NO_C
> AMELLIA -DOPENSSL_NO_SEED -DOPENSSL_NO_RC5 -DOPENSSL_NO_MDC2
> -DOPENSSL_NO_TLSEXT
>  -DOPENSSL_NO_KRB5 -DOPENSSL_NO_DYNAMIC_ENGINE -D_WINDLL  -c ms\uplink.c
> uplink.c
> ms\uplink.c(11) : fatal error C1083: Cannot open include file: 'windows.h':
> No s
> uch file or directory
> NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio
> 8\VC\BIN\c
> l.EXE"' : return code '0x2'
> Stop.
> ------------------------------
>
> Any suggestions?
>
> Thanks in advance.
>
>  Rich O'Brien
>  970 W Valley Parkway, #456
> Escondido, CA 92025
> [EMAIL PROTECTED]
> (760) 291-0081 Main
> (760) 807-1590 Cell/Mobile
> (760) 291-0070 FAX
> ------------------------------
>  **** The information in this message may be proprietary and/or
> confidential, and protected from disclosure. If the reader of this message
> is not the intended recipient, or an employee or agent responsible for
> delivering this message to the intended recipient, you are hereby notified
> that any dissemination, distribution or copying of this communication is
> strictly prohibited. If you have received this communication in error,
> please notify 1stTransaction Corporation immediately by replying to this
> message and deleting it from your computer. ****
>
>
>


-- 
Met vriendelijke groeten / Best regards,

Ger Hobbelt

--------------------------------------------------
web: http://www.hobbelt.com/
http://www.hebbut.net/
mail: [EMAIL PROTECTED]
mobile: +31-6-11 120 978
--------------------------------------------------

Reply via email to