Thanks again for the response, would you mind if I forwarded your email onto the technical people at Geoscience? As your questions go beyond my understanding. I have tried to answer what I could below.
From: K. Frank [mailto:kfrank29.c@...]
Sent: Tuesday, 20 April 2010 11:23
To: MinGW Users List
Subject: Re: [Mingw-users] MinGW for Windows 7 64 bit
Hello Craig -
On Mon, Apr 19, 2010 at 11:51 PM, Craig Palmer <CPalmer@...> wrote:
> Thank you for your prompt response,
> Again my apologies if I am going against the user list protocol.
> 1. I have unzipped the file and will see if I can follow your suggestions and update the path statement to run include the bin location.
> 2. We are running some modelling software (ANUGA Australian National University and Geoscience Australia) that uses MinGW.
Do you know, precisely, what you need mingw for? Do you actually need to compile something (i.e., take source code -- the original programming language
-- and translate
it into machine language so that you have a binary executable)? Or, is your ANUGA software already compiled for 64 bits, but it somehow "uses MinGW"?
If the latter, you probably only need the mingw dll's (dynamic link
programs compiled with mingw need to have available at run time. In this case, you would typically add the directory containing the dll's (probably something like ..\mingw\bin) to your path, or you could copy the dll's to the directory containing the programs that need them.
I have added c:\mingw\bin to my path statement. The ANUGA software has a compile_all.py script that we have to run after installing all the dependencies. Then we run a test_all.py script to make sure it is behaving properly. I have run these scripts but they do not get anywhere. I did receive one error message which was:
Warning (from warnings module): File C:\Python26\Lib\site-pacakages\numpy\core\__init__.py, line 5 import multiarray
Warnin: Windows 64 bits support is experimental, and only available for testing. You are advised not to use it in production. CRASHES ARE TO BE EXPECTED - PLEASE REPORT THEM TO NUMPY DEVELOPERS
But I cannot reproduce this error, now it just runs the script without seemingly doing anything.
> We have been limited in the size of our models by the memory limitations of Windows XP (32 bit). So we are hoping to migrate to the Windows 7 64 bit environment to overcome this limitation. The software is used extensively under linux (ubuntu) in native 64 bit (not by us as we are a windows site) and they currently only have an installer for 32 bit windows.
This makes it sound like you need to compile the ANUGA software for 64-bit windows.
(You said "they currently only have an installer for 32 bit windows.") Is this right?
We have a 32 bit windows installer which installs all the dependencies (Python first) and ANUGA in one go. So what I have done is just installed Python2.6 64 bit, then all the 64 bit dependencies one after the other. Then ANUGA, which they tell me will run in 64 bit on a 64 bit system (I will confirm this with Geoscience).
Then I have added the following to my PATH statement:
> We have been told that it should run with Windows 7 64 bit if we get all the components installed in 64 bit versions. We have installed the 32 bit version and it runs under Windows 7 but in 32 bit mode so we still have the memory limitations. The other components used by ANUGA are: Python, Numpy, ScientificPython, VTK, NetCDF & Pscyo. I have found windows 64 bit installers for each of these except Psyco which looks like is only 32 bit, but ANUGA will run without Psyco just slower, so it should not be a problem?
This makes it sound like you don't need to compile any of the other packages, since you say you have 64-bit versions of all of them. Is this right?
Yes that's correct, and why I wasn't sure of MinGW as I had 64bit installer versions of the other packages:
> I hope all this makes sense and I will let you know if I have any success.
> Here's the advice I got from Geoscience:
> "As you have found out, you need 64bit python to go with your 64bit Windows7. You also know that you need to install all the dependencies required for ANUGA, such as numpy, after installing the 64bit python. The kicker is that if any of those dependencies have C code in them, they must also be built for 64bit python. The thing to look for is if any of the binary install packages specify a 32/64bit architecture - if they do make sure you install the 64bit version. You are probably also aware that a dependency package must also match the version of python you have installed".
What advice does Geoscience give you about the ANUGA software? Do they tell you that you need to rebuild (i.e., compile) it for 64-bit windows, or do they say that you can use the ANUGA software out of the box, provided you get all of the dependencies squared away?
Yes but I will conform
If "all" you need to do is recompile the ANUGA stuff with 64-bit mingw, it ought to be doable. Given that the software works under native 64-bit linux, and assuming that the 32-bit windows version you mention is a version that was built with 32-bit mingw, there is a good chance that the ANUGA software might build correctly using 64-bit mingw, although it will probably require some effort on your part, and you'll probably have to play around a little to get your environment properly configured.
Try to find out in more detail exactly what it is you need to do (maybe from Geoscience).
Like I said before, I did manage to build some small test programs using 64-bit mingw, so I may be able to help you a little, if that's part of what you need to do.
Here is the latest response from Geoscience:
Hi Craig, compile_all requires gcc which comes from MinGW. If you're using a 64-bit machine, you need the 64 bit version of gcc. Unfortunately we don't have access to Windows 7 at work and it's difficult for us to test it here.
You need to setup an environmental variable called PYTHONPATH and add this path to it:
where ... depends on the setup on your system.
I'll get back to you after I have tried this.
> -----Original Message-----
> From: K. Frank [mailto:kfrank29.c@...]
> Hello Craig -
> On Mon, Apr 19, 2010 at 6:53 PM, Craig Palmer <CPalmer@...> wrote:
>> I know that the user list is for the windows 32 bit API, but could
>> you please point me in the right direction for getting some advice on
>> running minGW in a 64 bit environment?
> I also apologize if my response is off-topic for this list.
>> I have been trying to locate a MinGW installer for Windows 7 64 bit
>> to use with Python 2.6 (or 2.5)
>> What I have found is:
Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
MinGW-users mailing list
This list observes the Etiquette found at http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same. Disregard for the list etiquette may cause your account to be moderated.
You may change your MinGW Account Options or unsubscribe at:
This email, including attachments, is intended for the recipient only. The email may contain confidential or privileged information or be subject to copyright. If you are not the intended recipient you must not disclose, copy or use any part of the e-mail. Any opinion stated in this e-mail is not the opinion of Wollongong City Council unless stated or apparent from its contents. Wollongong City Council believes this e-mail to be free of virus or defect however the recipient is responsible to ensure it is virus-free.
If you receive this e-mail in error, please notify the sender and delete the e-mail immediately.
Wollongong City Council respects your privacy and our Privacy Management Plan is located at: http://www.wollongong.nsw.gov.au