On 4/6/2010 5:02 PM, Derrick Brashear wrote: > On Mon, Apr 5, 2010 at 7:48 PM, Simona Poilinca > <[email protected]> wrote: >> Hello, >> >> I'm trying to build openAFS on a 32-bit Windows environment and I have a >> problem with one device driver when trying to link. The error states >> util_cr.obj : error LNK2019: unresolved external symbol __SEH_epilog4_GS >> referenced in function _gencurdir >> util_cr.obj : error LNK2001: unresolved external symbol __except_handler4 >> util_cr.obj : error LNK2019: unresolved external symbol __SEH_prolog4_GS >> referenced in function _gencurdir >> C:\openAFS\openafs-1.5.73\obj\ >> i386_w2k\free\config\util_cr.exe : fatal error LNK1120: 3 unresolved >> externals > > I'd guess you're using the wrong version of Visual Studio, offhand. > I'm not an expert but a quick Google search of those symbols suggests > that.
The problem (as we discussed on #openafs IRC last night) is that the visual studio version and SDK version are incompatible. Things are especially difficult on Windows because the current tools distributed by Microsoft do not support Windows 2000 and pre-SP2 builds of XP and OpenAFS does support those platforms. The versions used for release builds are Visual Studio 2005 and either the XP SP2 SDK or the 2003 SP1 SDK and the 3700 version of the DDK. Unfortunately, none of those SDK or DDK releases are currently available and we aren't permitted to distribute them. I'm currently attempting to coerce the build system to permit OpenAFS to build with just the Windows/v6.1 SDK and the 7600 WDK (which includes the compiler and CRT libs). Such a build will not be useful for releases but could be used as the basis for future work. I will post when I am done. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
