#512 Unresolved external symbol _CLSID_MachineDebugManager

closed-fixed
Mark Hammond
5
2010-11-17
2010-10-21
Paul Carroll
No

Hi,

I've some (rather old) python scripts that I'm trying to get running on my 'new' computer. In particular, the scripts make use of the Mr. Hammond's Win32 extensions, and my new machine is a Windows 7x64 box, using VS 2008. I installed Python 2.7, and win32 build 214. On my first attempt to install (setup.py -p install), I got a compilation error -- the one described in bug #3084013. So, to resolve this error, I re-synced with the latest Win32 from CVS, and now when I attempt to install, it gets further but I then get the linker error "Unresolved external _CLISD_MachineDebugManager" when attempting to build axdebug.pyd

I tried both ehte x86 and x64 variants of the base python tool (v2.7) -- same result.

Any suggestions?

Thanks

/Paul

Discussion

  • stephane
    stephane
    2010-11-01

    I have the same pb. I am using python 2.6.4 and VS2008 on Win7 x64.

     
  • Erik Janssens
    Erik Janssens
    2010-11-10

    Same issue here, python 2.7, VS2008, windows sdk 7.1

     
  • Erik Janssens
    Erik Janssens
    2010-11-10

    this symbol seems to be located in pdm.dll, a dll includen with Internet Explorer

    no idea on how to link against it ??

     
  • Mark Hammond
    Mark Hammond
    2010-11-16

    • status: open --> pending-works-for-me
     
  • Mark Hammond
    Mark Hammond
    2010-11-16

    Actually,, I spoke too soon - I don't get the problem using the sdk included with vs2008 but do with the installed platform sdk I mentioned. I was confused by a combination of setup.py using an arbitrary installed SDK and some cmd-prompts having the mssdk env var set and some not. I'm trying to work out a fix.

     
  • Mark Hammond
    Mark Hammond
    2010-11-16

    • assigned_to: nobody --> mhammond
    • status: pending-works-for-me --> open-accepted
     
  • Mark Hammond
    Mark Hammond
    2010-11-17

    I've checked in a fix for this.

     
  • Mark Hammond
    Mark Hammond
    2010-11-17

    • status: open-accepted --> closed-fixed
     
  • I encountered the same problem; Win XP, VS 2008, MS SDK 7.0, Python 2.7. I'm trying to compile build 214, except for the win32job.i file, which I upgraded to v1.7 according to #3084013.

     
  • Reproduced the issue as well. Python 2.7, Win 7 x64, VS2010. Tried installing windows sdk7 afterwards or building using MingW. no success.

     
  • Mark Hammond
    Mark Hammond
    2010-12-06

    To the people still reporting problems here: have you updated to the current CVS trunk, and have you read and followed the updated instructions in setup.py?

     
  • As a matter of a fact, yes, I had not used the most recent version from the CVS repository (I didn't realize that the comments are sorted in reversed chronological order, so I thought that "I spoke too soon" came after "I've checked in a fix" :) . Once I exported the most recent version, the problem went away, so please disregard my comment.