WINCE5.0 : Build error after installing QFE Rollup_2010 RRS feed

  • Question

  • Hi all.

    I have installed WINCE QEF Rollup_2010:

     - WinCEPB50-101231-Product-Update-Rollup-Armv4I.msi

    Then I have the problem:

    ntlm.lib(ntlmssp.obj) : error LNK2019: unresolved external symbol SspGetChannelBindings referenced in function AcceptSecurityContext
    ntlm.lib(ntlmssp.obj) : error LNK2019: unresolved external symbol SspHashIscChannelBindings referenced in function SspHandleChallengeMessage
    ntlm.lib(Ctxtcli.obj) : error LNK2019: unresolved external symbol LsaIIsSuppressChannelBindingInfo referenced in function MsvpLm20GetNtlm3ChallengeResponse
    ntlm.lib(ctxtsrv.obj) : error LNK2019: unresolved external symbol SspVerifyAscChannelBindings referenced in function SsprHandleNtlmAuthenticateMessage
    D:\WINCE500\PBWorkspaces\PM250ENGH\WINCE500\PM250_ARMV4I\cesysgen\oak\target\ARMV4I\retail\ntlmssp.dll : fatal error LNK1120: 4 unresolved externals
    NMAKE : fatal error U1077: 'link' : return code '0x460'
    NMAKE : fatal error U1077: 'D:\WINCE500\sdk\bin\i386\nmake.exe' : return code '0x2'


    Who can help me?


    Monday, March 7, 2011 9:15 AM

All replies

  • Did you do a clean sysgen? See also:

    Good luck,

    Michel Verhagen, eMVP
    Check out my blog:

    Microsoft Embedded Partner
    Consultancy, training and development services.
    Monday, March 7, 2011 9:37 AM
  • Thanks to your reply.

    I used Platform builder 5.0 and execute "Build and sysgen" with the "Clean Brfore Building" option.

    Does this matter?

    Tuesday, March 8, 2011 1:10 AM
  • Yes, it does.  The “Build and Sysgen” build command is a bad choice for a number of reasons.  It is designed to build all of the source code in the %_WINCEROOT%\PUBLIC AND %_WINCEROOT%\PRIVATE trees before running Sysgen, and it’s used internally by Microsoft for that purpose.  It takes a much longer to execute than is needed to complete a proper, clean OS image build. It’s prone to failure because Platform Builder doesn’t include all of the source code needed to build all the OS components.  Finally, it can actually corrupt your PB build environment, forcing you to reinstall PB and all the updates to recover a working build system.

    It is recommended that you remove the ‘Build and Sysgen’ and ‘Rebuild and Sysgen’ commands from the ‘Advanced Build Commands’ menu by using the Tools->Customize menu and dragging Build and Sysgen command out of the menu and into the Customize dialog box.  This prevents you from accidently executing either of these commands in the future.

    The recommended build command to use to perform a clean build after installing QFEs or changing your OS configuration is the ‘Build’-> ‘Advanced Build Commands’ -> ‘Clean Sysgen’ command.  This is the IDE equivalent to the command “blddemo clean –q”.

    Tom Gensel PTG Systems, LLC
    Tuesday, March 8, 2011 2:56 AM
  • I have confirmed the "Clean Syszen" command by the "blddemo clean -q" command.

    But the problem is still the same.

    On the other hand, was released in November QFE is not a problem.

    I'm still confused.

    best regards. thanks.

    Wednesday, March 9, 2011 2:19 AM
  • If using Build and Sysgen caused the problem, and may have, then the solution will be to reinstall Platform Builder.  As Tom pointed out, you (which includes all of us) don't have the source code to rebuild the binaries that were removed by when you ran Build and Sysgen.

    On the other hand, I am not sure that this is the problem, I would have expected linker errors associated with not finding obj or lib files. 

    Certainly reinstalling would rule out the Build and Sysgen if it is not the problem.

    Bruce Eitman (eMVP)
    Senior Engineer
    Bruce.Eitman AT Eurotech DOT com
    My BLOG

    Eurotech Inc.
    Wednesday, March 9, 2011 3:03 AM