Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Error R6034 when starting VIM loading Python dynamically under Windows 7 #173

Closed
GoogleCodeExporter opened this issue Aug 18, 2015 · 4 comments
Closed

Error R6034 when starting VIM loading Python dynamically under Windows 7 #173

GoogleCodeExporter opened this issue Aug 18, 2015 · 4 comments
Labels
auto-migrated defect if_python platform-windows Priority-Medium

Comments

@GoogleCodeExporter
Copy link 

Under Windows 7 (64 Bit) my VIM builds produce an runtime error R6034 stating 
that an application attempts to use the C Runtime library in an incorrect 
manner. After two such message boxes VIM starts nevertheless but without Python 
support.

So far I understand the reports and solutions in the net about that error the 
root cause is that VIM loads the Python DLL (python27.dll in my case) 
_dynamically_ and Python loads the MSVC runtime DLL without having a correct 
manifest.

reference:
http://social.msdn.microsoft.com/Forums/vstudio/en-US/9fbc9292-11b8-4ee4-94a4-52
23546df280/r6034-attempt-to-load-c-runtime-library-without-using-manifest?forum=
vcgeneral

Original issue reported on code.google.com by ma...@von-oppen.com on 16 Oct 2013 at 4:19
@GoogleCodeExporter
Copy link
Author 

here for reference the original error message box...

Original comment by ma...@von-oppen.com on 17 Oct 2013 at 7:57

Attachments:

@GoogleCodeExporter
Copy link
Author 

There's a workaround for this problem posted @ SO 
http://stackoverflow.com/a/10257098/851055

Original comment by zaaghad@gmail.com on 6 Feb 2014 at 1:47

@GoogleCodeExporter
Copy link
Author 

Yes, thanks a lot. It is clear to me that this problem cannot be fixed from VIM 
point of view. It is annoying that I have to use this mt.exe utility on every 
system where I use VIM because on every system may be installed another version 
of the MSVC runtime DLLs.

I have a 3rd party AciveX application which loads the Python DLL and uses a 
different set of MSVC runtime DLLs depending from if it is called from Internet 
Explorer or Firefox. For that application there is no solution at all.

Maybe I should talk to the Python developers if they could provide a Python 
version with MSVC runtime statically linked into the Python DLL.

Original comment by ma...@von-oppen.com on 6 Feb 2014 at 8:29

@chrisbra
Copy link
Member

not sure if this is still valid, but closing, since it does not seem to be a Vim problem as mentioned in the last comment.

@jsit jsit mentioned this issue Jan 30, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated defect if_python platform-windows Priority-Medium
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@chrisbra @k-takata @GoogleCodeExporter