The NAG Fortran Compiler is available on Linux, Microsoft Windows and Mac OS X. The latest release (6.2) has extensive support for both modern and legacy Fortran features, and also supports parallel programming with OpenMP. NAG’s f95 compiler is the first of several products that NAG expects to bring to the Mac OS X platform over the next few months. ' The technical innovation and performance of Mac OS X as well as Apple’s commitment to serve the scientific and technical market has really impressed us, ' said Rob Meyer, president of NAG’s U.S. Affiliate, NAG. Nag_cbm95, nag_coverage95, nag_decs95, nag_fcalls95, nag_mkintf95, nag_modules95, nag_prest95, nag_struct95, nag_ustan95, and nag_xref95 and the NAGWare f95 Compiler allow you to specify other directories to search for ``.mod' files using the -I option. These tools need to be able to read ``.mod' files for any modules USEd that are not.
Hi, I'm trying to use F2PY on Mac OS 10.5 with G95, but I'm getting the error 'g95: unrecognized option '-shared'. I tried modifying the NumPy code to use the correct '-dynamic' flag, rather than the '-shared' flag. While that does allow for F2PY to successfully execute, I get the error Traceback (most recent call last): File ', line 1, in ImportError: dlopen(/Users/srunni/src/pdb2pqr/pdb2pqr/tinker/src/tinker/source/ese.so, 2): no suitable image found.
Did find: /Users/srunni/src/pdb2pqr/pdb2pqr/tinker/src/tinker/source/ese.so: unknown file type, first eight bytes: 0x80 0xC0 0x4F 0x00 0xEB 0x57 0xE0 0x8F when I attempt to import the generated module. Any ideas on how to fix this? Thanks, Samir Unni Numpy-discussion mailing list. I'm trying to use F2PY on Mac OS 10.5 with G95, but I'm getting the error 'g95: unrecognized option '-shared'. I tried modifying the NumPy code to use the correct '-dynamic' flag, rather than the '-shared' flag. While that does allow for F2PY to successfully execute, I get the error Traceback (most recent call last): File ', line 1, in ImportError: dlopen(/Users/srunni/src/pdb2pqr/pdb2pqr/tinker/src/tinker/source/ese.so2): no suitable image found.
Did find: /Users/srunni/src/pdb2pqr/pdb2pqr/tinker/src/tinker/source/ese.so: unknown file type, first eight bytes: 0x80 0xC0 0x4F 0x00 0xEB 0x57 0xE0 0x8F when I attempt to import the generated module. Any ideas on how to fix this? AFAIK g95 is not supported by numpy distutils on Mac OS X.
Cheers Adam Numpy-discussion mailing list. On Wed, Jun 10, 2009 at 12:44, Samir Unni wrote: I'm trying to use F2PY on Mac OS 10.5 with G95, but I'm getting the error 'g95: unrecognized option '-shared'. I tried modifying the NumPy code to use the correct '-dynamic' flag, rather than the '-shared' flag. While that does allow for F2PY to successfully execute, I get the error Traceback (most recent call last): File ', line 1, in ImportError: dlopen(/Users/srunni/src/pdb2pqr/pdb2pqr/tinker/src/tinker/source/ese.so2): no suitable image found. Did find: /Users/srunni/src/pdb2pqr/pdb2pqr/tinker/src/tinker/source/ese.so: unknown file type, first eight bytes: 0x80 0xC0 0x4F 0x00 0xEB 0x57 0xE0 0x8F when I attempt to import the generated module.
Any ideas on how to fix this? AFAIK g95 is not supported by numpy distutils on Mac OS X. Are you sure?
When I run 'f2py -c -help-fcompiler', I get: List of available Fortran compilers: -fcompiler=g95 G95 Fortran Compiler (0.91) G95 is the only compiler listed as available. If it can't be used, then what can? I would actually prefer to use GFortran, but that is not listed as available. Thanks, Samir Numpy-discussion mailing list. On Wed, Jun 10, 2009 at 15:04, Samir Unni wrote: Are you sure? When I run 'f2py -c -help-fcompiler', I get: List of available Fortran compilers: -fcompiler=g95 G95 Fortran Compiler (0.91) G95 is the only compiler listed as available. If it can't be usedthen what can?
I would actually prefer to use GFortran, but that is not listed as available. You might try running: C: Python25 Lib site-packages numpy f2py diagnose.py -Original Message- From: mailto: On Behalf Of Adam Mercer Sent: Wednesday, June 10, 2009 1:12 PM To: Discussion of Numerical Python Subject: Re: Numpy-discussion F2PY error with G95 on Mac OS 10.5 On Wed, Jun 10, 2009 at 15:04, Samir Unni wrote: Are you sure? When I run 'f2py -c -help-fcompiler', I get: List of available Fortran compilers: -fcompiler=g95 G95 Fortran Compiler (0.91) G95 is the only compiler listed as available. If it can't be usedthen what can? I would actually prefer to use GFortran, but that is not listed as available.
On Wed, Jun 10, 2009 at 15:04, Samir Unni wrote: Are you sure? When I run 'f2py -c -help-fcompiler', I get: List of available Fortran compilers: -fcompiler=g95 G95 Fortran Compiler (0.91) G95 is the only compiler listed as available. If it can't be usedthen what can? I would actually prefer to use GFortran, but that is not listed as available. As strange as it may sound, the same type of thing happened on my PC: it was working (i.e. Diagnose.py & example problem), then quit working after an uninstall of ipython, requiring a complete reinstall.
(see my previous post earlier today). On Wed, Jun 10, 2009 at 3:24 PM, Adam Mercer wrote: On Wed, Jun 10, 2009 at 15:19, Samir Unni wrote: That's odd. You're running Mac OS 10.5.7?
Nag F95 Compiler For Mac
Did you install NumPy manually or via Fink? Yep Intel 10.5.7, installed from MacPorts. MacPorts might be the difference then. I tried both the Fink and manual installs, and both are giving the same result. Do you think you could try doing the manual install and let me know if all those other compilers are still listed as available? Also, what version of Python are you using? Thanks, Samir Numpy-discussion mailing list.
On Wed, Jun 10, 2009 at 2:59 PM, Adam Mercer wrote: On Wed, Jun 10, 2009 at 12:44, Samir Unni wrote: I'm trying to use F2PY on Mac OS 10.5 with G95, but I'm getting the error 'g95: unrecognized option '-shared'. I tried modifying the NumPy code to use the correct '-dynamic' flag, rather than the '-shared' flag. While that does allow for F2PY to successfully execute, I get the error Traceback (most recent call last): File ', line 1, in ImportError: dlopen(/Users/srunni/src/pdb2pqr/pdb2pqr/tinker/src/tinker/source/ese.so2): no suitable image found. Did find: /Users/srunni/src/pdb2pqr/pdb2pqr/tinker/src/tinker/source/ese.so: unknown file type, first eight bytes: 0x80 0xC0 0x4F 0x00 0xEB 0x57 0xE0 0x8F when I attempt to import the generated module. Any ideas on how to fix this? AFAIK g95 is not supported by numpy distutils on Mac OS X. No it is not, at least not in your configuration: g95 cannot build universal binaries, and I think the OP error is caused by this.
Gfortran is certainly supported. I don't know about fink and darwin ports, but the gfortran compiler available at is the recommended one.
David Numpy-discussion mailing list. On Thu, Jun 11, 2009 at 5:04 AM, Samir Unni wrote: On Wed, Jun 10, 2009 at 2:59 PM, Adam Mercer wrote: On Wed, Jun 10, 2009 at 12:44, Samir Unni wrote: I'm trying to use F2PY on Mac OS 10.5 with G95, but I'm getting the error 'g95: unrecognized option '-shared'. I tried modifying the NumPy code to use the correct '-dynamic' flag, rather than the '-shared' flag. While that does allow for F2PY to successfully execute, I get the error Traceback (most recent call last): File ', line 1, in ImportError: dlopen(/Users/srunni/src/pdb2pqr/pdb2pqr/tinker/src/tinker/source/ese.so2): no suitable image found. Did find: /Users/srunni/src/pdb2pqr/pdb2pqr/tinker/src/tinker/source/ese.so: unknown file type, first eight bytes: 0x80 0xC0 0x4F 0x00 0xEB 0x57 0xE0 0x8F when I attempt to import the generated module. Any ideas on how to fix this?
AFAIK g95 is not supported by numpy distutils on Mac OS X. No it is not, at least not in your configuration: g95 cannot build universal binaries, and I think the OP error is caused by this. Gfortran is certainly supported. Running diagnose.py gives me this error: Couldn't match compiler version for 'GNU Fortran (GCC) 4.3.3 nCopyright (C) 2008 Free Software Foundation, Inc. N nGNU Fortran comes with NO WARRANTY, to the extent permitted by law. NYou may redistribute copies of GNU Fortran nunder the terms of the GNU General Public License. NFor more information about these matters, see the file named COPYING n' Is this the source of the problem?
I looked at numpy/distutils/tests/testfcompilergnu.py, and I found this: gfortranversionstrings = ('GNU Fortran 95 (GCC 4.0.3 20051023 (prerelease) (Debian 4.0.2-3))', '4.0.3'), ('GNU Fortran 95 (GCC) 4.1.0', '4.1.0'), ('GNU Fortran 95 (GCC) 4.2.0 20060218 (experimental)', '4.2.0'), ('GNU Fortran (GCC) 4.3.0 20070316 (experimental)', '4.3.0')My GNU Fortran version string is 'GNU Fortran (GCC) 4.3.3'. However, even after adding it to that list and reinstalling, the issue persisted. Thanks, Samir Numpy-discussion mailing list. On Wed, Jun 10, 2009 at 8:32 PM, David Cournapeau wrote: On Thu, Jun 11, 2009 at 5:04 AM, Samir Unni wrote: On Wed, Jun 10, 2009 at 2:59 PM, Adam Mercer wrote: On Wed, Jun 10, 2009 at 12:44, Samir Unni wrote: I'm trying to use F2PY on Mac OS 10.5 with G95, but I'm getting the error 'g95: unrecognized option '-shared'.
I tried modifying the NumPy code to use the correct '-dynamic' flag, rather than the '-shared' flag. While that does allow for F2PY to successfully execute, I get the error Traceback (most recent call last): File ', line 1, in ImportError: dlopen(/Users/srunni/src/pdb2pqr/pdb2pqr/tinker/src/tinker/source/ese.so2): no suitable image found. Did find: /Users/srunni/src/pdb2pqr/pdb2pqr/tinker/src/tinker/source/ese.so: unknown file type, first eight bytes: 0x80 0xC0 0x4F 0x00 0xEB 0x57 0xE0 0x8F when I attempt to import the generated module. Any ideas on how to fix this? AFAIK g95 is not supported by numpy distutils on Mac OS X. No it is not, at least not in your configuration: g95 cannot build universal binaries, and I think the OP error is caused by this. Gfortran is certainly supported.
SIR2 includes high definition impulse responses (HDIR) of *real* places produced by Pinguin, Hamburg. It offers zero-latency processing with low CPU-consumption and non-destructive audio processing of impulse responses.
Running diagnose.py gives me this error: Ignore diagnose.py for the time being - what does f2py says? Is this the source of the problem? I looked at numpy/distutils/tests/testfcompilergnu.py, and I found this: gfortranversionstrings = ('GNU Fortran 95 (GCC 4.0.3 20051023 (prerelease) (Debian 4.0.2-3))'4.0.3')('GNU Fortran 95 (GCC) 4.1.0', '4.1.0')('GNU Fortran 95 (GCC) 4.2.0 20060218 (experimental)', '4.2.0')('GNU Fortran (GCC) 4.3.0 20070316 (experimental)', '4.3.0')My GNU Fortran version string is 'GNU Fortran (GCC) 4.3.3'. Howevereven after adding it to that list and reinstalling, the issue persisted. Yes, this just looks like a unit test, so it won't change anything to numpy.distutils behavior. David Numpy-discussion mailing list. On Thu, Jun 11, 2009 at 11:58 AM, David Cournapeau wrote: Ignore diagnose.py for the time being - what does f2py says?
Running build running configfc running buildsrc building extension 'ese' sources f2py options: adding '/tmp/tmpFElPq/src.macosx-10.5-i386-2.5/fortranobject.c' to sources. Adding '/tmp/tmpFElPq/src.macosx-10.5-i386-2.5' to includedirs.