build + install worked fine.
My CPU is Intel not AMD so I apparently had a bogus python install.
--
View this message in context:
http://python.6.n6.nabble.com/PyCrypto-builds-neither-with-MSVC-nor-MinGW-tp4366880p4986058.html
Sent from the Python - python-list mailing list archive at Nabble.com
On 08/22/2012 02:21 PM, bikewave wrote:
I also had the unresolved externals problem (not the mdir.h problem, though)
and my solution was different.
a) reinstall correct python2.6.4, using an Intel-flavor msi vice
AMD64-flavor
b) source the c:\program files(x86\microsoft visual studio
Oh wait, just realised it was loading the (x86) tools. Doing a quick
search I noticed that I didn't have the x64 components installed, so
loading up the MSVC08 setup again and installing it, then:
copying vcvarsamd64.bat to vcvarsall.bat and adding its directory
(C:\Program Files (x86)\Microsoft
Nope, I have C:\Python27 (and C:\Python27\Scripts) in my PATH.
C:\workingdir\pycryptowhere python
C:\Python27\python.exe
On Tue, Mar 13, 2012 at 4:44 PM, Case Van Horsen cas...@gmail.com wrote:
On Mon, Mar 12, 2012 at 9:57 PM, Alec Taylor alec.tayl...@gmail.com wrote:
Hmm, I just tried that
On a brand new Windows install now, with a brand new VS8 installed
with new YASM and MPIR in c:\usr\src\include and c:\usr\src\lib.
But it still isn't working:
C:\workingdir\pycryptopython setup.py build_ext -Ic:\usr\src\include
-Lc:\usr\src\lib install
running build_ext
warning: GMP or MPIR
FYI: When running vcvarsall manually, I get a variety of linker
errors, even though I have the SDK and everything else installed:
running build_ext
building 'Crypto.Random.OSRNG.winrandom' extension
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\cl.exe /c
/nologo /Ox /MD /W3 /GS-
On Monday, March 12, 2012 1:38:29 PM UTC-7, Alec Taylor wrote:
On a brand new Windows install now, with a brand new VS8 installed
with new YASM and MPIR in c:\usr\src\include and c:\usr\src\lib.
But it still isn't working:
This was a little challenging. I looked through the setup.py to
Hmm, I just tried that method, but the output I got was still:
C:\workingdir\pycryptopython setup.py install
running install
running build
running build_py
running build_ext
building 'Crypto.Random.OSRNG.winrandom' extension
Traceback (most recent call last):
File setup.py, line 452, in module
On Tue, Feb 7, 2012 at 9:37 PM, Alec Taylor alec.tayl...@gmail.com wrote:
Thanks all for your replies.
I have now installed MSVC8 and YASM.
I assume you installed Visual Studio. I've omitted the commands to use
the SDK compiler below.
I was able to successfully run configure.bat and make.bat
Thanks, but to get it to work with pip, wouldn't I need to add it to
PATH? - Or can I just add those library args to pip?
On Wed, Feb 8, 2012 at 9:48 PM, Case Van Horsen cas...@gmail.com wrote:
On Tue, Feb 7, 2012 at 9:37 PM, Alec Taylor alec.tayl...@gmail.com wrote:
Thanks all for your
On Wed, Feb 8, 2012 at 4:24 AM, Alec Taylor alec.tayl...@gmail.com wrote:
Thanks, but to get it to work with pip, wouldn't I need to add it to
PATH? - Or can I just add those library args to pip?
I don't think so. pyCrypto probably builds a single DLL so the MPIR library is
statically linked
Thanks all for your replies.
I have now installed MSVC8 and YASM.
I was able to successfully run configure.bat and make.bat (including
make.bat check).
However, I'm unsure what to do about install, since there is no
install arg. Do I copy it across to my VC\bin folder, or does it need
it's own
On Mon, Feb 6, 2012 at 6:39 PM, Terry Reedy tjre...@udel.edu wrote:
On 2/6/2012 1:53 AM, Chris Angelico wrote:
I suppose there's no chance of moving to a free compiler?
VC express is free-as-in-beer. The whole V. Studio is free to core
developers. MS may not *like* open-source software, but
On Feb 5, 6:40 am, Alec Taylor alec.tayl...@gmail.com wrote:
PIL, PyCrypto and many other modules require a C compiler and linker.
Unfortunately neither install on my computer, with a PATH with the following:
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC
PIL, PyCrypto and many other modules require a C compiler and linker.
Unfortunately neither install on my computer, with a PATH with the following:
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC
C:\libraries\MinGW\msys\1.0\bin
C:\libraries\MinGW
C:\Python27\Scripts
Output from
Am 05.02.2012 15:40, schrieb Alec Taylor:
PIL, PyCrypto and many other modules require a C compiler and linker.
Unfortunately neither install on my computer, with a PATH with the following:
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC
C:\libraries\MinGW\msys\1.0\bin
A 4 year old compiler?
I also have MSVC11 installed. Can the python project add support for
that so that we aren't waiting 5 years between compiler support?
On Mon, Feb 6, 2012 at 2:23 AM, Christian Heimes li...@cheimes.de wrote:
Am 05.02.2012 15:40, schrieb Alec Taylor:
PIL, PyCrypto and many
On Mon, 06 Feb 2012 03:42:08 +1100, Alec Taylor wrote:
A 4 year old compiler?
Compilers aren't like milk. They don't go off after a few weeks. A good
compiler/operating system combination should still be usable after 4 or
14 years. The compiler I'm using is six years old, and I expect that it
On 2/5/2012 6:23 PM, Dennis Lee Bieber wrote:
On Mon, 6 Feb 2012 03:42:08 +1100, Alec Tayloralec.tayl...@gmail.com
wrote:
A 4 year old compiler?
I also have MSVC11 installed. Can the python project add support for
that so that we aren't waiting 5 years between compiler support?
3.3 will
On Mon, Feb 6, 2012 at 12:26 PM, Terry Reedy tjre...@udel.edu wrote:
On 2/5/2012 6:23 PM, Dennis Lee Bieber wrote:
On Mon, 6 Feb 2012 03:42:08 +1100, Alec Tayloralec.tayl...@gmail.com
wrote:
A 4 year old compiler?
I also have MSVC11 installed. Can the python project add support for
that
On 2/6/2012 1:53 AM, Chris Angelico wrote:
On Mon, Feb 6, 2012 at 12:26 PM, Terry Reedytjre...@udel.edu wrote:
On 2/5/2012 6:23 PM, Dennis Lee Bieber wrote:
On Mon, 6 Feb 2012 03:42:08 +1100, Alec Tayloralec.tayl...@gmail.com
wrote:
A 4 year old compiler?
I also have MSVC11 installed. Can
21 matches
Mail list logo
