[prev in list] [next in list] [prev in thread] [next in thread]
List: mingw-users
Subject: [Mingw-users] how to invoke (install?) mingw64.
From: patrick flaherty <patf () well ! com>
Date: 2009-04-23 20:11:27
Message-ID: 49F0CB6F.4060606 () well ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi,
I successfully built the Sourceforge pyOpenSSL project with mingw32.
But I'm on a 64-bit machine and have had problems with loading the
project's DLLs at runtime (on a 32 bit machine loading the DLLs works
fine) and when I found mingw-64 on sourceforge thought I'd give it a try
and see if it helped me out on my 64 bit machine. The code will
eventually need to be deployed on 64 bit machines.
Downloaded a recent toolchain build. The instructions I used are here:
http://mingw-w64.wiki.sourceforge.net/Installation+of+binary+toolchain+packages
So I can copy the whole of the toolchain directory structure to any
directory location; add the bin directory within the toolchain to my
PATH; and at least according to the instructions above I should be good
to go.
Yeah right.
The compile quickly exits with:
> L:\MyID\Python\pyOpenSSL>setup.py build_ext -Ic:\openssl\include -c
> x86_64-pc-mingw32
> running build_ext
> error: don't know how to compile C/C++ code on platform 'nt' with
> 'x86_64-pc-mingw32' compiler
Looking around the web, I /believe/ x86_64-pc-mingw32 to be the correct
name to be use. However when I look under where I installed mingw64, I
find 3 bin directories:
> pat$ pwd
> /cygdrive/d/mingw64
> pat$ find . -name bin
> ./bin
> ./mingw/bin
> ./x86_64-pc-mingw32/bin
> pat$
I originally set the location in PATH to the first of the 3. Didn't
work. And then I tried #s 2 and 3 and they provoked exactly the same
error from the build.
pat
[Attachment #5 (text/html)]
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
Hi,<br>
<br>
I successfully built the Sourceforge pyOpenSSL project with mingw32.<br>
<br>
But I'm on a 64-bit machine and have had problems with loading the
project's DLLs at runtime (on a 32 bit machine loading the DLLs works
fine) and when I found mingw-64 on sourceforge thought I'd give it a
try and see if it helped me out on my 64 bit machine. The code will
eventually need to be deployed on 64 bit machines.<br>
<br>
Downloaded a recent toolchain build. The instructions I used are
here: <br>
<br>
<a class="moz-txt-link-freetext" \
href="http://mingw-w64.wiki.sourceforge.net/Installation+of+binary+toolchain+packages" \
>http://mingw-w64.wiki.sourceforge.net/Installation+of+binary+toolchain+packages</a><br>
>
<br>
So I can copy the whole of the toolchain directory structure to any
directory location; add the bin directory within the toolchain to my
PATH; and at least according to the instructions above I should be good
to go.<br>
<br>
Yeah right.<br>
<br>
The compile quickly exits with:<br>
<br>
<blockquote type="cite">L:\MyID\Python\pyOpenSSL>setup.py build_ext
-Ic:\openssl\include -c x86_64-pc-mingw32<br>
running build_ext<br>
error: don't know how to compile C/C++ code on platform 'nt' with
'x86_64-pc-mingw32' compiler</blockquote>
Looking around the web, I <i>believe</i> x86_64-pc-mingw32 to be the
correct name to be use. However when I look under where I installed
mingw64, I find 3 bin directories:<br>
<blockquote type="cite">pat$ pwd<br>
/cygdrive/d/mingw64<br>
pat$ find . -name bin<br>
./bin<br>
./mingw/bin<br>
./x86_64-pc-mingw32/bin<br>
pat$ <br>
</blockquote>
I originally set the location in PATH to the first of the 3. Didn't
work. And then I tried #s 2 and 3 and they provoked exactly the same
error from the build.<br>
<br>
pat<br>
<br>
<br>
<br>
</body>
</html>
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
--
_______________________________________________
MinGW-users mailing list
MinGW-users@lists.sourceforge.net
This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.
Most annoying abuses are:
1) Top posting
2) Thread hijacking
3) HTML/MIME encoded mail
4) Improper quoting
5) Improper trimming
_______________________________________________
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic