Re: Build Problem With VC7 (VS.NET 2003)
openssl-0.9.7b builds successfully for me with VC2003. Both DLL and static version for Release/Debug. That error about __ftol2 normally means that .obj files built by vc7+ is being linked by vc6. Try to make sure that vc6 is not being mixed up with vc7 in any way. Are you using "Visual Studio .NET 2003 Command Prompt" window where all the environment is setup right for vc7? - Original Message - From: "Kevin Williams" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, June 28, 2003 6:03 PM Subject: Build Problem With VC7 (VS.NET 2003) > Trying to build OpenSSL v0.9.7b on Windows with VC++ - the version that > comes with Visual Studio .NET 2003. First, I got these errors: > > link /nologo /subsystem:console /machine:I386 /opt:ref /dll > /out:out32dll\libeay32.dll /def:ms/LIBEAY32.def > @C:\DOCUME~1\Kevin\LOCALS~1\Temp\nm433.tmp > ms/LIBEAY32.def(7) : warning LNK4017: DESCRIPTION statement not > supported for the target platform; ignored >Creating library out32dll\libeay32.lib and object > out32dll\libeay32.exp > b_print.obj : error LNK2019: unresolved external symbol __ftol2 > referenced in function _roundv > b_print.obj : error LNK2019: unresolved external symbol __aulldvrm > referenced in function _fmtint > out32dll\libeay32.dll : fatal error LNK1120: 2 unresolved externals > NMAKE : fatal error U1077: 'link' : return code '0x460' > Stop. > > I found this article on MSDN that helps with the __ftol2 function: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/ > html/vcrefQIfistSuppress_ftol.asp > > Adding /QIfist to CFLAG in ntdll.mak makes the __ftol2 warning go away > (you might want to put that in the official ntdll.mak). > > I cannot, however, figure out what fmtint in b_print.c is doing that > causes this __aulldvrm error. It seems that __aulldvrm might have > existed in strmbasd.lib in VC6 (as part of DirectX possibly?) but > strmbasd.lib doesn't exist in my VC7 directory anywhere. Does anyone > have a clue for me? I REALLY REALLY want to use OpenSSL in the new > VC++! > > -Kevin > > > __ > OpenSSL Project http://www.openssl.org > User Support Mailing List[EMAIL PROTECTED] > Automated List Manager [EMAIL PROTECTED] __ OpenSSL Project http://www.openssl.org User Support Mailing List[EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
RE: Build Problem With VC7 (VS.NET 2003)
> I cannot, however, figure out what fmtint in b_print.c is doing > that causes this __aulldvrm error. Never mind - since I have VC++ 6.0 available as well, I just decided to switch to using that instead. OpenSSL v0.9.7b compiled perfectly on the first try and the DLLs work great under VC++ 7.0. I'd prefer not to do it this way, but I'll probably only ever compile the OpenSSL DLLs once (at least, once per release) so I can live with it. Thanks, -Kevin __ OpenSSL Project http://www.openssl.org User Support Mailing List[EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Build Problem With VC7 (VS.NET 2003)
On Sat, Jun 28, 2003, Kevin Williams wrote: > Trying to build OpenSSL v0.9.7b on Windows with VC++ - the version that > comes with Visual Studio .NET 2003. First, I got these errors: > > link /nologo /subsystem:console /machine:I386 /opt:ref /dll > /out:out32dll\libeay32.dll /def:ms/LIBEAY32.def > @C:\DOCUME~1\Kevin\LOCALS~1\Temp\nm433.tmp > ms/LIBEAY32.def(7) : warning LNK4017: DESCRIPTION statement not > supported for the target platform; ignored >Creating library out32dll\libeay32.lib and object > out32dll\libeay32.exp > b_print.obj : error LNK2019: unresolved external symbol __ftol2 > referenced in function _roundv > b_print.obj : error LNK2019: unresolved external symbol __aulldvrm > referenced in function _fmtint > out32dll\libeay32.dll : fatal error LNK1120: 2 unresolved externals > NMAKE : fatal error U1077: 'link' : return code '0x460' > Stop. > > I found this article on MSDN that helps with the __ftol2 function: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/ > html/vcrefQIfistSuppress_ftol.asp > > Adding /QIfist to CFLAG in ntdll.mak makes the __ftol2 warning go away > (you might want to put that in the official ntdll.mak). > > I cannot, however, figure out what fmtint in b_print.c is doing that > causes this __aulldvrm error. It seems that __aulldvrm might have > existed in strmbasd.lib in VC6 (as part of DirectX possibly?) but > strmbasd.lib doesn't exist in my VC7 directory anywhere. Does anyone > have a clue for me? I REALLY REALLY want to use OpenSSL in the new > VC++! > Disclaimer: I don't have VC++ for Visual studio .NET 2003 nor do I have access to it. It sounds like a library or header conflict somewhere and that either an older library is referencing a now deleted symbol or a newer library is referencing one that didn't exist in the older version. I've checked under VC++ 6 against tmp32dll using: dumpbin /symbols b_print.obj and it produces a reference to __ftol but not __ftol2 or __aulldvrm. You could try using dumpbin against the various libraries and DLLs to see if the symbols are defined anywhere. Steve. -- Dr Stephen N. Henson. Core developer of the OpenSSL project: http://www.openssl.org/ Freelance consultant see: http://www.drh-consultancy.demon.co.uk/ Email: [EMAIL PROTECTED], PGP key: via homepage. __ OpenSSL Project http://www.openssl.org User Support Mailing List[EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
