|
From: SourceForge.net <no...@so...> - 2010-10-21 18:02:28
|
Bugs item #3092278, was opened at 2010-10-21 14:02 Message generated for change (Tracker Item Submitted) made by cameraguy You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: installation Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Paul Carroll (cameraguy) Assigned to: Nobody/Anonymous (nobody) Summary: Unresolved external symbol _CLSID_MachineDebugManager Initial Comment: 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 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-11-01 13:32:51
|
Bugs item #3092278, was opened at 2010-10-21 20:02 Message generated for change (Comment added) made by stephane42 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: installation Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Paul Carroll (cameraguy) Assigned to: Nobody/Anonymous (nobody) Summary: Unresolved external symbol _CLSID_MachineDebugManager Initial Comment: 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 ---------------------------------------------------------------------- Comment By: stephane (stephane42) Date: 2010-11-01 14:32 Message: I have the same pb. I am using python 2.6.4 and VS2008 on Win7 x64. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-11-10 13:12:36
|
Bugs item #3092278, was opened at 2010-10-21 18:02 Message generated for change (Comment added) made by tw55413 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: installation Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Paul Carroll (cameraguy) Assigned to: Nobody/Anonymous (nobody) Summary: Unresolved external symbol _CLSID_MachineDebugManager Initial Comment: 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 ---------------------------------------------------------------------- Comment By: Erik Janssens (tw55413) Date: 2010-11-10 13:12 Message: Same issue here, python 2.7, VS2008, windows sdk 7.1 ---------------------------------------------------------------------- Comment By: stephane (stephane42) Date: 2010-11-01 13:32 Message: I have the same pb. I am using python 2.6.4 and VS2008 on Win7 x64. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-11-10 13:39:21
|
Bugs item #3092278, was opened at 2010-10-21 18:02 Message generated for change (Comment added) made by tw55413 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: installation Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Paul Carroll (cameraguy) Assigned to: Nobody/Anonymous (nobody) Summary: Unresolved external symbol _CLSID_MachineDebugManager Initial Comment: 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 ---------------------------------------------------------------------- Comment By: Erik Janssens (tw55413) Date: 2010-11-10 13:39 Message: this symbol seems to be located in pdm.dll, a dll includen with Internet Explorer no idea on how to link against it ?? ---------------------------------------------------------------------- Comment By: Erik Janssens (tw55413) Date: 2010-11-10 13:12 Message: Same issue here, python 2.7, VS2008, windows sdk 7.1 ---------------------------------------------------------------------- Comment By: stephane (stephane42) Date: 2010-11-01 13:32 Message: I have the same pb. I am using python 2.6.4 and VS2008 on Win7 x64. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-11-16 05:01:56
|
Bugs item #3092278, was opened at 2010-10-22 05:02 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: installation Group: None >Status: Pending >Resolution: Works For Me Priority: 5 Private: No Submitted By: Paul Carroll (cameraguy) Assigned to: Nobody/Anonymous (nobody) Summary: Unresolved external symbol _CLSID_MachineDebugManager Initial Comment: 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 ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2010-11-16 16:01 Message: I can't reproduce this when using a later platform SDK - I've updated setup.py to reflect a new build environment I just setup - for VS2008 I had to use the Windows SDK for Windows 7 from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6b6c21d2-2006-4afa-9702-529fa782d63b ---------------------------------------------------------------------- Comment By: Erik Janssens (tw55413) Date: 2010-11-11 00:39 Message: this symbol seems to be located in pdm.dll, a dll includen with Internet Explorer no idea on how to link against it ?? ---------------------------------------------------------------------- Comment By: Erik Janssens (tw55413) Date: 2010-11-11 00:12 Message: Same issue here, python 2.7, VS2008, windows sdk 7.1 ---------------------------------------------------------------------- Comment By: stephane (stephane42) Date: 2010-11-02 00:32 Message: I have the same pb. I am using python 2.6.4 and VS2008 on Win7 x64. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-11-16 06:38:58
|
Bugs item #3092278, was opened at 2010-10-22 05:02 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: installation Group: None >Status: Open >Resolution: Accepted Priority: 5 Private: No Submitted By: Paul Carroll (cameraguy) >Assigned to: Mark Hammond (mhammond) Summary: Unresolved external symbol _CLSID_MachineDebugManager Initial Comment: 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 ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2010-11-16 17:38 Message: 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. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-16 16:01 Message: I can't reproduce this when using a later platform SDK - I've updated setup.py to reflect a new build environment I just setup - for VS2008 I had to use the Windows SDK for Windows 7 from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6b6c21d2-2006-4afa-9702-529fa782d63b ---------------------------------------------------------------------- Comment By: Erik Janssens (tw55413) Date: 2010-11-11 00:39 Message: this symbol seems to be located in pdm.dll, a dll includen with Internet Explorer no idea on how to link against it ?? ---------------------------------------------------------------------- Comment By: Erik Janssens (tw55413) Date: 2010-11-11 00:12 Message: Same issue here, python 2.7, VS2008, windows sdk 7.1 ---------------------------------------------------------------------- Comment By: stephane (stephane42) Date: 2010-11-02 00:32 Message: I have the same pb. I am using python 2.6.4 and VS2008 on Win7 x64. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-11-17 05:25:48
|
Bugs item #3092278, was opened at 2010-10-22 05:02 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: installation Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Paul Carroll (cameraguy) Assigned to: Mark Hammond (mhammond) Summary: Unresolved external symbol _CLSID_MachineDebugManager Initial Comment: 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 ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2010-11-17 16:25 Message: I've checked in a fix for this. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-16 17:38 Message: 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. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-16 16:01 Message: I can't reproduce this when using a later platform SDK - I've updated setup.py to reflect a new build environment I just setup - for VS2008 I had to use the Windows SDK for Windows 7 from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6b6c21d2-2006-4afa-9702-529fa782d63b ---------------------------------------------------------------------- Comment By: Erik Janssens (tw55413) Date: 2010-11-11 00:39 Message: this symbol seems to be located in pdm.dll, a dll includen with Internet Explorer no idea on how to link against it ?? ---------------------------------------------------------------------- Comment By: Erik Janssens (tw55413) Date: 2010-11-11 00:12 Message: Same issue here, python 2.7, VS2008, windows sdk 7.1 ---------------------------------------------------------------------- Comment By: stephane (stephane42) Date: 2010-11-02 00:32 Message: I have the same pb. I am using python 2.6.4 and VS2008 on Win7 x64. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-12-04 01:33:06
|
Bugs item #3092278, was opened at 2010-10-21 22:02 Message generated for change (Comment added) made by mikhailedoshin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: installation Group: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Paul Carroll (cameraguy) Assigned to: Mark Hammond (mhammond) Summary: Unresolved external symbol _CLSID_MachineDebugManager Initial Comment: 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 ---------------------------------------------------------------------- Comment By: Mikhail Edoshin (mikhailedoshin) Date: 2010-12-04 04:33 Message: 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. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-17 08:25 Message: I've checked in a fix for this. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-16 09:38 Message: 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. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-16 08:01 Message: I can't reproduce this when using a later platform SDK - I've updated setup.py to reflect a new build environment I just setup - for VS2008 I had to use the Windows SDK for Windows 7 from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6b6c21d2-2006-4afa-9702-529fa782d63b ---------------------------------------------------------------------- Comment By: Erik Janssens (tw55413) Date: 2010-11-10 16:39 Message: this symbol seems to be located in pdm.dll, a dll includen with Internet Explorer no idea on how to link against it ?? ---------------------------------------------------------------------- Comment By: Erik Janssens (tw55413) Date: 2010-11-10 16:12 Message: Same issue here, python 2.7, VS2008, windows sdk 7.1 ---------------------------------------------------------------------- Comment By: stephane (stephane42) Date: 2010-11-01 16:32 Message: I have the same pb. I am using python 2.6.4 and VS2008 on Win7 x64. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-12-06 08:30:56
|
Bugs item #3092278, was opened at 2010-10-21 18:02 Message generated for change (Comment added) made by nitro-12 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: installation Group: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Paul Carroll (cameraguy) Assigned to: Mark Hammond (mhammond) Summary: Unresolved external symbol _CLSID_MachineDebugManager Initial Comment: 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 ---------------------------------------------------------------------- Comment By: Ricardo Nuno Almeida (nitro-12) Date: 2010-12-06 08:30 Message: Reproduced the issue as well. Python 2.7, Win 7 x64, VS2010. Tried installing windows sdk7 afterwards or building using MingW. no success. ---------------------------------------------------------------------- Comment By: Mikhail Edoshin (mikhailedoshin) Date: 2010-12-04 01:33 Message: 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. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-17 05:25 Message: I've checked in a fix for this. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-16 06:38 Message: 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. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-16 05:01 Message: I can't reproduce this when using a later platform SDK - I've updated setup.py to reflect a new build environment I just setup - for VS2008 I had to use the Windows SDK for Windows 7 from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6b6c21d2-2006-4afa-9702-529fa782d63b ---------------------------------------------------------------------- Comment By: Erik Janssens (tw55413) Date: 2010-11-10 13:39 Message: this symbol seems to be located in pdm.dll, a dll includen with Internet Explorer no idea on how to link against it ?? ---------------------------------------------------------------------- Comment By: Erik Janssens (tw55413) Date: 2010-11-10 13:12 Message: Same issue here, python 2.7, VS2008, windows sdk 7.1 ---------------------------------------------------------------------- Comment By: stephane (stephane42) Date: 2010-11-01 13:32 Message: I have the same pb. I am using python 2.6.4 and VS2008 on Win7 x64. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-12-06 21:44:58
|
Bugs item #3092278, was opened at 2010-10-22 05:02 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: installation Group: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Paul Carroll (cameraguy) Assigned to: Mark Hammond (mhammond) Summary: Unresolved external symbol _CLSID_MachineDebugManager Initial Comment: 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 ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2010-12-07 08:44 Message: 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? ---------------------------------------------------------------------- Comment By: Ricardo Nuno Almeida (nitro-12) Date: 2010-12-06 19:30 Message: Reproduced the issue as well. Python 2.7, Win 7 x64, VS2010. Tried installing windows sdk7 afterwards or building using MingW. no success. ---------------------------------------------------------------------- Comment By: Mikhail Edoshin (mikhailedoshin) Date: 2010-12-04 12:33 Message: 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. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-17 16:25 Message: I've checked in a fix for this. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-16 17:38 Message: 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. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-16 16:01 Message: I can't reproduce this when using a later platform SDK - I've updated setup.py to reflect a new build environment I just setup - for VS2008 I had to use the Windows SDK for Windows 7 from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6b6c21d2-2006-4afa-9702-529fa782d63b ---------------------------------------------------------------------- Comment By: Erik Janssens (tw55413) Date: 2010-11-11 00:39 Message: this symbol seems to be located in pdm.dll, a dll includen with Internet Explorer no idea on how to link against it ?? ---------------------------------------------------------------------- Comment By: Erik Janssens (tw55413) Date: 2010-11-11 00:12 Message: Same issue here, python 2.7, VS2008, windows sdk 7.1 ---------------------------------------------------------------------- Comment By: stephane (stephane42) Date: 2010-11-02 00:32 Message: I have the same pb. I am using python 2.6.4 and VS2008 on Win7 x64. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-12-07 08:33:29
|
Bugs item #3092278, was opened at 2010-10-21 22:02 Message generated for change (Comment added) made by mikhailedoshin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: installation Group: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Paul Carroll (cameraguy) Assigned to: Mark Hammond (mhammond) Summary: Unresolved external symbol _CLSID_MachineDebugManager Initial Comment: 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 ---------------------------------------------------------------------- Comment By: Mikhail Edoshin (mikhailedoshin) Date: 2010-12-07 11:33 Message: 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. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-12-07 00:44 Message: 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? ---------------------------------------------------------------------- Comment By: Ricardo Nuno Almeida (nitro-12) Date: 2010-12-06 11:30 Message: Reproduced the issue as well. Python 2.7, Win 7 x64, VS2010. Tried installing windows sdk7 afterwards or building using MingW. no success. ---------------------------------------------------------------------- Comment By: Mikhail Edoshin (mikhailedoshin) Date: 2010-12-04 04:33 Message: 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. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-17 08:25 Message: I've checked in a fix for this. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-16 09:38 Message: 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. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-16 08:01 Message: I can't reproduce this when using a later platform SDK - I've updated setup.py to reflect a new build environment I just setup - for VS2008 I had to use the Windows SDK for Windows 7 from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6b6c21d2-2006-4afa-9702-529fa782d63b ---------------------------------------------------------------------- Comment By: Erik Janssens (tw55413) Date: 2010-11-10 16:39 Message: this symbol seems to be located in pdm.dll, a dll includen with Internet Explorer no idea on how to link against it ?? ---------------------------------------------------------------------- Comment By: Erik Janssens (tw55413) Date: 2010-11-10 16:12 Message: Same issue here, python 2.7, VS2008, windows sdk 7.1 ---------------------------------------------------------------------- Comment By: stephane (stephane42) Date: 2010-11-01 16:32 Message: I have the same pb. I am using python 2.6.4 and VS2008 on Win7 x64. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018 |
