[issue25223] Statically or dynamically linked to the VC++runtime ? or how Python install fails on Vista despite the VC redist packages - api-ms-win-crt-runtime-l1-1-0.dll

2015-09-25 Thread acx01bc

acx01bc added the comment:

@steve.dower : the vc_redist packages doesn't list the files it installs, I'm 
not sure of the names of the files, but who cares, please look at my screenshot 
of dependency walker, it shows how different versions of Python win32 releases 
that I downloaded on python.org (3.5.0, 3.4.3,3.3.x) used different vc-runtime 
settings, and how some of them don't work on Vista.

@Wolfgang Langner : "this update doesn't apply to you system" :-)

So what I'm saying is : please be careful with the compiler options if you want 
you executables to be compatible with vista/7/8/10

--

___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25223>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue25223] Statically or dynamically linked to the VC++runtime ? or how Python install fails on Vista despite the VC redist packages - api-ms-win-crt-runtime-l1-1-0.dll

2015-09-25 Thread acx01bc

Changes by acx01bc <acx...@gmail.com>:


--
status: open -> closed

___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25223>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue25223] Statically or dynamically linked to the VC++runtime ? or how Python install fails on Vista despite the VC redist packages - api-ms-win-crt-runtime-l1-1-0.dll

2015-09-24 Thread acx01bc

acx01bc added the comment:

On Vista32bits, the VC++2015 redist package does install msvcr140.dll but none 
of the api-ms-win-crt-***-l1-1-0.dll, thus (that's why I opened this discussion 
at first) it is impossible to make many of the Python releases working, at 
least on Vista 32bits.
There are many compiler options about the msvcr***.dll (platform 
V100,V110,V120,V140.., statically or dynamically linked to the C runtime, 
multi-threaded or not...) and obviously the settings used to build Python 3.4.3 
work fine on Vista (platform V100), while the settings used to build Python 
3.5.0 don't (platform V140).

--

___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25223>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue25223] Statically or dynamically linked to the VC++runtime ? or how Python install fails o Vista despite the VC redist packages - api-ms-win-crt-runtime-l1-1-0.dll

2015-09-23 Thread acx01bc

New submission from acx01bc:

I think you should build Python.exe with the option to be statically linked to 
the VC++-runtime. This way, the executable is a little bigger, but you ensure 
nobody will have troubles with some VC-runtime different Dll versions.

DETAILS : (I posted it also there 
http://stackoverflow.com/questions/32748932/python-3-4-3-works-on-windows-vista-but-not-3-5-0-because-of-vc-redist-package
 )

I am on Windows Vista 32bits. I downloaded Python 3.5.0 but I got the famous 
api-ms-win-crt-runtime-l1-1-0.dll problem. Then I installed many Visual C++ 
Redistributable Packages (I tried the 2015's one, then 2013, and 2012) but none 
of these packages installed any .dll of the correct name. Then, I tried to 
download a previous version of Python, the 3.3.2 win32 release, I got the same 
problem !

> Then, I downloaded the Python 3.4.3 Win32 release, and this-one worked 
immediately. I suspect that version to have been statically linked with the 
VC-runtime. This clearly lacks of coherence, some Python releases work, while 
others don't. So I hope some of the Python developers will see that message and 
will be able to build some binaries compatible with Windows Vista and the 
VC-redist-packages.

Question : did anyone understand where that api-ms-win-crt-runtime-l1-1-0.dll 
comes from ? I suppose it is related to the VC++ compiler options used when 
building Python.exe (on my VS2010 I have the options code generation/runtime 
library/multi-threaded, static or dynamic and general/platform_toolset, V100, 
V110, V120 or V140) ?

--
components: Installation
messages: 251463
nosy: acx01bc
priority: normal
severity: normal
status: open
title: Statically or dynamically linked  to the VC++runtime ? or how Python 
install fails o Vista despite the VC redist packages - 
api-ms-win-crt-runtime-l1-1-0.dll
type: crash
versions: Python 3.5

___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25223>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue25223] Statically or dynamically linked to the VC++runtime ? or how Python install fails on Vista despite the VC redist packages - api-ms-win-crt-runtime-l1-1-0.dll

2015-09-23 Thread acx01bc

Changes by acx01bc <acx...@gmail.com>:


--
title: Statically or dynamically linked  to the VC++runtime ? or how Python 
install fails o Vista despite the VC redist packages - 
api-ms-win-crt-runtime-l1-1-0.dll -> Statically or dynamically linked  to the 
VC++runtime ? or how Python install fails on Vista despite the VC redist 
packages - api-ms-win-crt-runtime-l1-1-0.dll

___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25223>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue25223] Statically or dynamically linked to the VC++runtime ? or how Python install fails on Vista despite the VC redist packages - api-ms-win-crt-runtime-l1-1-0.dll

2015-09-23 Thread acx01bc

acx01bc added the comment:

With dependency walker I see that :
- in 3.4.3, Python34.exe and also Python.34.dll have been dynamically linked 
with msvcr100.dll (platform target : v100 in Visual C++ project properties), 
- while  in 3.5.0 (the one you download on python.org main page) Python35.exe 
and Python35.dll have been dynamically linked with msvcr140.dll and many other 
dlls (platform v140).

--
Added file: http://bugs.python.org/file40558/python_dll_problem.jpg

___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25223>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com