Cantera 2.0 Install fails on OS X 10.7.3 due to Fortran errors

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install XCode 4.3, and install the command line developer tools to provide 
command line access to llvm-gcc-4.2.1 and llvm-g++-4.2.1.
2. Install gfortran 4.2.1 from http://r.research.att.com/tools/ (see the link 
under "gcc-4.2 (Apple build 5666.3) with GNU Fortran 4.2.4 for Mac OS X 10.7 
(Lion)").
3. Clone the Cantera repository using git-svn.
4. Within the cloned Cantera repository directory, execute the command "sudo 
scons build" at the shell prompt using the cantera.conf file as follows:

python_package = 'full'
python_cmd = '/Library/Frameworks/Python.framework/Versions/2.7/bin/python'
matlab_toolbox = 'y'
matlab_path = '/Applications/MATLAB_R2012a.app'
F90 = 'gfortran-4.2'
F77 = 'gfortran-4.2'

5. Execute the command "sudo scons install" at the shell prompt upon successful 
completion of the build. The install process fails. 

What is the expected output? What do you see instead?
I expect to see a successful install. I've included the output from the build 
in an attached text file. The problem has to do with compilation of Fortran 
files. It might be worthwhile to include information on how to install a 
compatible Fortran compiler in the install docs.

What version of the product are you using? On what operating system?
I cloned the Cantera SVN repository last night (April 30, 2012). I'm using:
- Mac OS X 10.7.3
- Python 2.7
- XCode 4.3 (with the LLVM versions of Apple's builds of gcc 4.2.1 and g++ 
4.2.1)
- gfortran 4.2.1 (Apple Inc. build 5666.3)
- MATLAB R2012a
- Boost 1.49
- Subversion 1.6.17
- Git 1.7.7.5 (Apple Git-26)
- NumPy 1.7

Original issue reported on code.google.com by goxbe...@gmail.com on 2 May 2012 at 1:48

Attachments:

• CanteraBuildOutput.txt

[GoogleCodeExporter]

If the Fortran 90 interface is not built, then the build and install is 
successful. Also, the *.mod files that are needed for the build of the Fortran 
90 interface appear to be in the wrong locations (in the root directory of the 
build rather than in the src/fortran subdirectory. Since side effects sometimes 
must be accounted for manually in SCons, it's possible that the paths for these 
Fortran module files are not pointing in the right place.

Original comment by goxbe...@gmail.com on 2 May 2012 at 2:49

[GoogleCodeExporter]

What happens if you change line 683 of the SConstruct file to read:
    if 'gfortran' in env['F90']:

Original comment by yarmond on 3 May 2012 at 7:11

• Changed state: Accepted

[GoogleCodeExporter]

Fixed in r1445.

Original comment by yarmond on 7 May 2012 at 6:26

• Changed state: Fixed