Re: Problem building 3.5 on Windows
Mark, Excuse the format of this post, stuck on the road only with an iPhone but in the event it helps, http://blog.vrplumber.com/b/2014/02/12/step-2-get-amd64-compatible-vs-2010/ may be useful. Jlc -- https://mail.python.org/mailman/listinfo/python-list
Re: Problem building 3.5 on Windows
On 17/05/2014 20:08, Chris Angelico wrote: On Sun, May 18, 2014 at 5:06 AM, Mark Lawrence wrote: Solved as you got me looking in a different direction. It certainly helps if you have an up to date version of the SDK :) Hah. I don't know which versions of Visual Studio Express go with which versions of Python, but I know there is a strict correspondence (in terms of official builds and support, at least). ChrisA I have Visual Studio Express 2010 but the SDK was 7.0 instead of 7.1. I'm now waiting for the Visual Studio Express 2010 SP1 which fixes the linker problem. And I've just got "restart now to finsih installing" after maybe one hour:) -- My fellow Pythonistas, ask not what our language can do for you, ask what you can do for our language. Mark Lawrence --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com -- https://mail.python.org/mailman/listinfo/python-list
Re: Problem building 3.5 on Windows
On Sun, May 18, 2014 at 5:06 AM, Mark Lawrence wrote: > Solved as you got me looking in a different direction. It certainly helps > if you have an up to date version of the SDK :) Hah. I don't know which versions of Visual Studio Express go with which versions of Python, but I know there is a strict correspondence (in terms of official builds and support, at least). ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: Problem building 3.5 on Windows
On 17/05/2014 18:05, Chris Angelico wrote: On Sun, May 18, 2014 at 2:59 AM, Mark Lawrence wrote: 1>..\PC\make_versioninfo.c(1): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory What stupid thing have I forgotten, apart from switching to *nix? :) Well, apart from that... I'd guess you have a pathing problem. Since stdio.h is a standard compiler-provided header, I'd advise locating it on disk, then checking if that path is in the INCLUDE env var. Not sure if the Python build process overrides that, though, but it's a start. ChrisA Solved as you got me looking in a different direction. It certainly helps if you have an up to date version of the SDK :) -- My fellow Pythonistas, ask not what our language can do for you, ask what you can do for our language. Mark Lawrence --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com -- https://mail.python.org/mailman/listinfo/python-list
Re: Problem building 3.5 on Windows
On Sun, May 18, 2014 at 2:59 AM, Mark Lawrence wrote: > 1>..\PC\make_versioninfo.c(1): fatal error C1083: Cannot open include file: > 'stdio.h': No such file or directory > > What stupid thing have I forgotten, apart from switching to *nix? :) Well, apart from that... I'd guess you have a pathing problem. Since stdio.h is a standard compiler-provided header, I'd advise locating it on disk, then checking if that path is in the INCLUDE env var. Not sure if the Python build process overrides that, though, but it's a start. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
