[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20020429: NetCDF and Lahey Fortran PROv6.1: missing libfj9i6.so



CYTu,

> To: <address@hidden>
> From: "CYTu" <address@hidden>
> Subject: Compile NetCDF with Lahey/Fujitsu Fortran PROv6.1 failed......
> Organization: Airlab701
> Keywords: 200204290718.g3T7Iva28776 netCDF 3.5 Mandrake Lahey Fortran 
> cfortran.h

The above message contained the following:

> Hello
> As title, I tried several ways to solve this probelm, and didn't get any =
> progress. Basically I reference to 4 hompages and followed their =
> instructions.
> 1.http://www.unidata.ucar.edu/glimpse/netcdfgroup-list/1473
> 2.http://www.unidata.ucar.edu/projects/coohl/mhonarc/MailArchives/netcdf/=
> msg04094.html
> 3.http://www.cwr.uwa.edu.au/~slawinski/work/netcdfinfo.html#linux
> 4.http://www.knmi.nl/onderzk/CKO/install-netcdf.html
> 
> In the 4th homepage, it provides "-DLahetFortran" option for CPPFLAGS by =
> downloading another "cfortran.h" and replacing the old one. This seems =
> to be the correct solution by re-writing a new header files for =
> Lahey/Fujitsu Fortran. Unfortunately I still got error messages.
> 
> The machine is Mandrake 8.1 Linux PC. I follwed the instruction in the =
> last section " Reporting Problems" in the "INSATLL.html" .Below is what =
> I did and what I got.=20
> 
> #################### VERSION =
> ##################################################################
> 3.5.0
> 
> #################### run configure =
> ##################################################################
> CC=3D/usr/bin/cc Cxx=3D=3D/usr/bin/g++ FC=3D/home/lf95/bin/lf95 =
> F90=3D/home/lf95/bin/lf95 CPPFLAGS=3D-DpgiFortran CFLAGS=3D-O =
> FFLAGS=3D-O ./configure >configure.log 2>&1=20
> 
> #################### configure.log =
> ##################################################################
> creating cache ./config.cache
> checking for top-level source-directory
> /home/netcdf-3.5/src
> checking for m4 preprocessor
> checking for m4... m4
> checking m4 flags... -B10000
> checking C compiler "cc"... works
> checking how to make dependencies... false
> checking for CC... no
> checking for cxx... no
> checking for c++... c++
> checking C++ compiler "c++"... works
> checking how to run the C preprocessor... cc -E
> checking user-defined Fortran-77 compiler "lf95"... works
> checking for Fortran .F compiler...=20
> checking if Fortran-77 compiler handles *.F files... yes
> checking user-defined Fortran-90 compiler "lf95"... works
> checking for nm utility
> checking for nm... nm
> checking nm flags...=20
> checking for C-equivalent to Fortran routine "SUB"... sub_
> checking for Fortran "byte"... yes
> checking for Fortran "integer*2"... yes
> checking if Fortran "byte" is C "signed char"... no
> checking if Fortran "byte" is C "short"... no
> checking if Fortran "byte" is C "int"... no
> checking if Fortran "byte" is C "long"... no

The last 4 lines above indicate that the configure script couldn't find
a C primitive type equivalent to the Fortran "byte" type.  This is very
bad and must be resolved in order to build the Fortran interface of the
netCDF package.

The reason for the problem can be found in the configure-script
error-message file "config.log":

> #################### config.log =
> ##################################################################
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
...
> configure:1933: checking if Fortran "byte" is C "signed char"
> configure:1942: cc -c -DpgiFortran -O conftest.c
> configure:1944: lf95 -O -c conftestf.f
> Encountered 0 errors, 0 warnings in file conftestf.f.
> configure:1946: lf95 -o conftest -O  conftestf.o conftest.o=20
> configure:1948: ./conftest
> ./conftest: error while loading shared libraries: libfj9i6.so.1: cannot =
> open shared object file: No such file or directory
...

It appears that your Lahey Fortran-95 compiler (lf95) couldn't compile
a very simple test program.  This indicates a severe problem with your
Lahey Fortran-95 development environment.  I suggest that you consult
with your system administrator regarding the last error message above.
When that problem is fixed, then retry building the netCDF pacakge.

Regards,
Steve Emmerson   <http://www.unidata.ucar.edu>