[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20000504: f90 build problem: can't find f77 routines: Absoft, Linux
- Subject: 20000504: f90 build problem: can't find f77 routines: Absoft, Linux
- Date: Tue, 02 May 2000 15:34:25 -0600
Bruce,
> Date: Tue, 2 May 2000 17:11:04 -0400 (EDT)
> From: root <address@hidden>
> To: address@hidden
> Cc: address@hidden, address@hidden
> Subject: 20000504:f90 build problem: can't find f77 routines
> Organization: Dept. Of Geography/University Of Toronto
> Keywords: 200005012042.e41KgZG24064
In the above message you wrote:
> Thanks for your rapid reply. The library files are in place. I think
> everything is fine, and still get the same eorror. There are 9 attached
> files: 1-5 are the netCDF building log files, 6 is system info file, 7 is
> the f90 building log file, and 8-9 are the library files. Thanks for any
> advise.
[enclosures removed]
By using the "nm" utility on a Linux system, I discovered that the
Fortran routines in your netCDF library, "libnetcdf.a", are named like
the following:
nf_inq_libvers__
whereas, the Absoft Fortran compiler is looking for names like this:
NF_INQ_LIBVERS
It appears, therefore, that a FUNDAMENTAL INCOMPATIBILITY exists between
the naming conventions used by your "g77" compiler and the Absoft
Fortran-90 compiler. (This is lamentable but not surprising.)
I suggest that you try rebuilding the netCDF package using the Absoft
Fortran compiler as the *only* Fortran compiler:
1. Go to the top-level, netCDF, source-directory.
2. Perform steps 3 and 4 near the end of the INSTALL file.
3. Perform step 5 near the end of the INSTALL file with the
following exceptions:
a. Ensure that the environment variable FC is set to "f90"
(an absolute pathname would be best -- but I couldn't
determine from your information what it was); and
b. Ensure that the environment variable CPPFLAGS does *not*
contain the string "-Df2cFortran".
4. Perform steps 6 through 9 near the end of the INSTALL file.
Please let me know if this helps.
Regards,
Steve Emmerson <http://www.unidata.ucar.edu>