[issue4431] Distutils MSVC doesn't create manifest file (with fix)
Pavel Repin added the comment: I'd like to point out that on some configurations (at least mine), you really need to specify /MANIFEST option to the linker, even though MSDN documentation seems to imply that /MANIFEST behavior is ON by default. My config: beta version of Windows 7 ActivePython 2.6.1.1 MSVS 2008 with 32-bit C/C++ Optimizing Compiler Version 15.00.21022.08 for 80x86 -- keywords: +patch nosy: +paxan Added file: http://bugs.python.org/file13124/0001-Ensure-the-assembly-manifest-file-generation-is-gene.patch ___ Python tracker <http://bugs.python.org/issue4431> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4431] Distutils MSVC doesn't create manifest file (with fix)
Pavel Repin added the comment: Hi Marc,I am pretty sure it helped on my particular configuration. I was trying to compile MySQL-python-1.2.2.tar.gz package from source and it was failing in mt.exe step because the manifest file was not there. I didn't do anything special on my machine. I have 3 versions of MSVS installed cleanly side-by-side (which is a legit scenario): MSVS 2003, MSVS 2005, and MSVS 2008. All at the latest patch levels. No standalone PlatformSDKs are installed. Besides, if you just ignore the obscure blurb about /MANIFEST option being default in MSDN, and read the descriptions of both /MANIFEST and /MANIFESTFILE options, you would agree that it will not do any harm to be explicit and always have /MANIFEST option passed to linker. I'm going to do one more experiment with a different machine, this time it will be Vista (not W7) with a similar MSVS setup. I will report my findings. On Tue, Feb 17, 2009 at 2:08 PM, Marc-Andre Lemburg wrote: > > Marc-Andre Lemburg added the comment: > > On 2009-02-17 20:22, Pavel Repin wrote: > > Pavel Repin > > added the comment: > > > > I'd like to point out that on some configurations (at least mine), you > > really need to specify /MANIFEST option to the linker, even though MSDN > > documentation seems to imply that /MANIFEST behavior is ON by default. > > My config: > > beta version of Windows 7 > > ActivePython 2.6.1.1 > > MSVS 2008 with 32-bit C/C++ Optimizing Compiler Version 15.00.21022.08 > > for 80x86 > > Are you sure ? > > We've had such a request before and the reason for MSVC not generating > a .manifest file was some setting the user had done on his system. > > FWIW: distutils generates those files just fine for me. > > Then again, it probably doesn't hurt just adding the option. > > ___ > Python tracker > <http://bugs.python.org/issue4431> > ___ > Added file: http://bugs.python.org/file13126/unnamed ___ Python tracker <http://bugs.python.org/issue4431> ___Hi Marc,I am pretty sure it helped on my particular configuration.I was trying to compile MySQL-python-1.2.2.tar.gz package from source and it was failing in mt.exe step because the manifest file was not there. I didn't do anything special on my machine. I have 3 versions of MSVS installed cleanly side-by-side (which is a legit scenario): MSVS 2003, MSVS 2005, and MSVS 2008. All at the latest patch levels. No standalone PlatformSDKs are installed. Besides, if you just ignore the obscure blurb about /MANIFEST option being default in MSDN, and read the descriptions of both /MANIFEST and /MANIFESTFILE options, you would agree that it will not do any harm to be explicit and always have /MANIFEST option passed to linker. I'm going to do one more experiment with a different machine, this time it will be Vista (not W7) with a similar MSVS setup. I will report my findings. On Tue, Feb 17, 2009 at 2:08 PM, Marc-Andre Lemburg <mailto:rep...@bugs.python.org"; target="_blank">rep...@bugs.python.org> wrote: Marc-Andre Lemburg <mailto:m...@egenix.com"; target="_blank">m...@egenix.com> added the comment: On 2009-02-17 20:22, Pavel Repin wrote: > Pavel Repin <mailto:prepin%2bpythonb...@gmail.com"; target="_blank">prepin+pythonb...@gmail.com> added the comment: > > I'd like to point out that on some configurations (at least mine), you > really need to specify /MANIFEST option to the linker, even though MSDN > documentation seems to imply that /MANIFEST behavior is ON by default. > My config: > beta version of Windows 7 > ActivePython 2.6.1.1 > MSVS 2008 with 32-bit C/C++ Optimizing Compiler Version 15.00.21022.08 > for 80x86 Are you sure ? We've had such a request before and the reason for MSVC not generating a .manifest file was some setting the user had done on his system. FWIW: distutils generates those files just fine for me. Then again, it probably doesn't hurt just adding the option. ___ Python tracker <mailto:rep...@bugs.python.org"; target="_blank">rep...@bugs.python.org> <http://bugs.python.org/issue4431"; target="_blank">http://bugs.python.org/issue4431> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4431] Distutils MSVC doesn't create manifest file (with fix)
Pavel Repin added the comment:
Marc-Andre,
I can also repro this on Vista machine with the same Python & MSVS
configuration.
This is the build error stemming from missing manifest file
(unnecessary details elided; note the absence of /MANIFEST option):
C:\src\MySQL-python-1.2.2>python setup.py -v bdist_egg
...
...\link.exe /DLL /nologo /INCREMENTAL:NO "/LIBPATH:C:\Program
Files\MySQL\MySQL Server 5.0\lib\opt" /LIBPATH:C:\Python26\libs
/LIBPATH:C:\Python26\PCbuild kernel32.lib advapi32.lib wsock32.lib
mysqlclient.lib /EXPORT:init_mysql
build\temp.win32-2.6\Release\_mysql.obj
/OUT:build\lib.win32-2.6\_mysql.pyd
/IMPLIB:build\temp.win32-2.6\Release\_mysql.lib
/MANIFESTFILE:build\temp.win32-2.6\Release\_mysql.pyd.manifest
Creating library build\temp.win32-2.6\Release\_mysql.lib and object
build\temp.win32-2.6\Release\_mysql.exp
...
...\mt.exe -nologo -manifest
build\temp.win32-2.6\Release\_mysql.pyd.manifest
-outputresource:build\lib.win32-2.6\_mysql.pyd;2
build\temp.win32-2.6\Release\_mysql.pyd.manifest : general error
c1010070: Failed to load and parse the manifest. The system cannot
find the file specified.
error: command 'mt.exe' failed with exit status 31
The error goes away when I hack msvc9compiler.py to have:
ld_args.append('/MANIFEST')
See patch attached to the bug.
On Tue, Feb 17, 2009 at 2:34 PM, Pavel Repin wrote:
>
> Pavel Repin added the comment:
>
> Hi Marc,I am pretty sure it helped on my particular configuration.
> I was trying to compile MySQL-python-1.2.2.tar.gz package from source and it
> was failing in mt.exe step because the manifest file was not there.
> I didn't do anything special on my machine. I have 3 versions of MSVS
> installed cleanly side-by-side (which is a legit scenario): MSVS 2003, MSVS
> 2005, and MSVS 2008. All at the latest patch levels. No standalone
> PlatformSDKs are installed.
>
> Besides, if you just ignore the obscure blurb about /MANIFEST option being
> default in MSDN, and read the descriptions of both /MANIFEST and
> /MANIFESTFILE options, you would agree that it will not do any harm to be
> explicit and always have /MANIFEST option passed to linker.
>
> I'm going to do one more experiment with a different machine, this time it
> will be Vista (not W7) with a similar MSVS setup. I will report my findings.
>
> On Tue, Feb 17, 2009 at 2:08 PM, Marc-Andre Lemburg
> wrote:
>
> >
> > Marc-Andre Lemburg added the comment:
> >
> > On 2009-02-17 20:22, Pavel Repin wrote:
> > > Pavel Repin >
> > added the comment:
> > >
> > > I'd like to point out that on some configurations (at least mine), you
> > > really need to specify /MANIFEST option to the linker, even though MSDN
> > > documentation seems to imply that /MANIFEST behavior is ON by default.
> > > My config:
> > > beta version of Windows 7
> > > ActivePython 2.6.1.1
> > > MSVS 2008 with 32-bit C/C++ Optimizing Compiler Version 15.00.21022.08
> > > for 80x86
> >
> > Are you sure ?
> >
> > We've had such a request before and the reason for MSVC not generating
> > a .manifest file was some setting the user had done on his system.
> >
> > FWIW: distutils generates those files just fine for me.
> >
> > Then again, it probably doesn't hurt just adding the option.
> >
> > ___
> > Python tracker
> > <http://bugs.python.org/issue4431>
> > ___
> >
>
> Added file: http://bugs.python.org/file13126/unnamed
>
> ___
> Python tracker
> <http://bugs.python.org/issue4431>
> ___
___
Python tracker
<http://bugs.python.org/issue4431>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4431] Distutils MSVC doesn't create manifest file
Changes by Pavel Repin : -- nosy: -paxan ___ Python tracker <http://bugs.python.org/issue4431> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
