Re: unresolved external symbol in VS8 from VS6

I have yet solved it!!

Here is the solution to this problem:
http://www.pcreview.co.uk/forums/thread-1428747.php

The problem was here:

"When getting the errors:

error LNK2001: unresolved external symbol ___security_cookie
error LNK2001: unresolved external symbol @__security_check_cookie@4

in Visual Studio .NET, it is likely that another library is being pulled
into the project. Add the /verbose:lib switch to the Linker command line
and do a rebuild all. This will output all of the libraries that are being
searched. If you see any libs that live in folders that are not part of
the Microsoft Visual Studio .NET install folder and you are not sure why
they are there, then that is probably the cause of this problem.

Go to Tools | Options | Projects | VC++ Directories and in the Include
Files and Library Files directories check for additional paths that should
not be there."

I used a path in the library files option and then it took a library that
was wrong instead of the right VS8 library. I have put that path at the end
of the library file options and now everything goes fine!! :-)


"JIGE" <nacho@xxxxxxxx> escribió en el mensaje
news:esrssd$aea$1@xxxxxxxxxxxxxxxxxxx
Hi again,

I have just created a new MFC project with Visual Studio 8 and it gives
the same errors... Debug version works while release version doesn´t link.
All the code is on default, so I haven´t wrriten anything this time...

What do I have to change to solve this problem? :-(

It gives me these errors on the default MFC project for release
version:

Linking...
pruebaMFC.obj : error LNK2001: unresolved external symbol
@__security_check_cookie@4
mfcs80.lib(stdafx.obj) : error LNK2001: unresolved external symbol
@__security_check_cookie@4
atls.lib(atltrace.obj) : error LNK2001: unresolved external symbol
@__security_check_cookie@4
stdafx.obj : error LNK2001: unresolved external symbol
__imp___resetstkoflw
mfcs80.lib(stdafx.obj) : error LNK2001: unresolved external symbol
__imp___resetstkoflw
stdafx.obj : error LNK2001: unresolved external symbol __imp___recalloc
mfcs80.lib(stdafx.obj) : error LNK2001: unresolved external symbol
__imp___recalloc
stdafx.obj : error LNK2001: unresolved external symbol __imp__wcscpy_s
mfcs80.lib(stdafx.obj) : error LNK2001: unresolved external symbol
__imp__wcscpy_s
mfcs80.lib(stdafx.obj) : error LNK2001: unresolved external symbol
__SEH_epilog4_GS
mfcs80.lib(stdafx.obj) : error LNK2001: unresolved external symbol
__except_handler4
mfcs80.lib(stdafx.obj) : error LNK2001: unresolved external symbol
__SEH_prolog4_GS
mfcs80.lib(stdafx.obj) : error LNK2001: unresolved external symbol
__alloca_probe_16
mfcs80.lib(stdafx.obj) : error LNK2001: unresolved external symbol
___CxxFrameHandler3
mfcs80.lib(stdafx.obj) : error LNK2001: unresolved external symbol
__EH_epilog3_GS
mfcs80.lib(stdafx.obj) : error LNK2001: unresolved external symbol
__EH_prolog3_GS
mfcs80.lib(stdafx.obj) : error LNK2001: unresolved external symbol
___security_cookie
atls.lib(atltrace.obj) : error LNK2001: unresolved external symbol
___security_cookie
mfcs80.lib(stdafx.obj) : error LNK2001: unresolved external symbol
__EH_prolog3
D

Thanks again!!

JIGE

"JIGE" <nacho@xxxxxxxx> escribió en el mensaje
news:esrrgc$ac5$1@xxxxxxxxxxxxxxxxxxx
Hi,

I have just converted an application from Visual Studio 6 to Visual
Studio 8 and it works fine under debug version, but it doesn´t work under
release.

It compiles without any problem, but it gives me a lot of linked
errors, like these:

CImage.obj : error LNK2001: unresolved external symbol __alloca_probe_16

mfcs80.lib(stdafx.obj) : error LNK2001: unresolved external symbol
___CxxFrameHandler3

mfcs80.lib(stdafx.obj) : error LNK2019: unresolved external symbol
__SEH_epilog4_GS referenced in function "bool __cdecl
ATL::_ATL_SAFE_ALLOCA_IMPL::_AtlVerifyStackAvailable(unsigned long)"
(?_AtlVerifyStackAvailable@_ATL_SAFE_ALLOCA_IMPL@ATL@@YA_NK@Z)

I have revised my app property pages, and I have changed all the
different properties and now the only difference between debug and
release versions is Configuration properties\C/C++\Code
Generation\Runtime Library, where it is Multi-threaded Debug DLL (/MDd)
for debug version and Multi-threaded DLL (/MD) for release version.

Release version only works if I put Multi-threaded Debug DLL (/MDd)
for that option, but obviously, that isn´t a good solution because
really I would work with a debug version instead a release version.

Do you know how to solve this problem?

Thanks in advance,

JIGE





.

Relevant Pages

  • RE: Missing Lib Files
    ... I've found that strange errors tend to go away after a clean sysgen. ... Consider using a build window (if you're in Visual Studio right click your ... libraries and header files. ... unresolved external symbol DisableThreadLibraryCalls referenced in function ...
    (microsoft.public.windowsce.platbuilder)
  • Re: linking error
    ... It is clear that the libraries you are loading are inconsistent in some way. ... 1>client.obj: error LNK2019: unresolved external symbol ...
    (microsoft.public.vc.mfc)
  • Re: Where can I get MFC70
    ... Where can I find mfc70d.lib and its associated dll? ... debug versions of the MS libraries are not redistributable. ... You need to either obtain the source code, or get the authors to recompile the library for your version of Visual Studio. ...
    (microsoft.public.dotnet.languages.vc)
  • Re: Where can I get MFC70
    ... DLLs that it references)? ... debug versions of the MS libraries are not redistributable. ... the library for your version of Visual Studio. ...
    (microsoft.public.dotnet.languages.vc)
  • Re: c++ app runs under Visual, crash in windows
    ... you execute a application from visual studio it will run in debug ... i.e it will use debug run time libraries. ...
    (microsoft.public.vc.language)