This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Curtis, >Date: Thu, 04 Dec 1997 10:14:47 -0800 >From: Curtis Williams <address@hidden> >Organization: San Diego Supercomputer Center >To: Steve Emmerson <address@hidden> >Subject: Re: 971204: build problems on Cray T90: can't find Fortran compiler >Keywords: 199712040119.SAA07244 In the above message, you wrote: > Oops. Sorry dude. The FORTRAN ENV variable was located in the Makefile > located at ./fortran/Makefile line 88 This is unrelated to your problem. That "FORTRAN" not an environment variable. It's an m4(1) macro used to determine which manual page is generated (C or Fortran). > > I don't get it? All of the T90 compiler env variables are set by my > default shell in the same module. Why are the c89 and CC compilers > visible yet f90 seemingly nonexistent? That's why I tried to change the > fortran directory Makefile. That didn't work either? Hmmmmm? On our Cray J90 I have the following in my ksh(1) initialization file in order to obtain the Fortran compilers: # Load modules. . /opt/modules/modules/init/ksh module load modules PrgEnv I need this *even if* I directly invoke the Fortran compiler by absolute pathname. Do you need something similar? > ./configure --prefix=/sdsc/dev/apps/netCDF/netcdf_src_dir/ > loading cache ./config.cache > checking for m4... (cached) m4 > checking for xlc... (cached) c89 > checking C compiler... works > checking how to make dependencies... false > checking for CC... (cached) CC > checking C++ compiler "CC"... works > checking how to run the C preprocessor... (cached) c89 -E > checking user-defined FORTRAN compiler "/opt/ctl/bin/f90"... configure: > warning: /opt/ctl/bin/f90 failed to compile test program The above indicates a serious problem. The reason should be in the file "config.log". > checking for FORTRAN .F compiler... > checking for FORTRAN preprocessor... /opt/ctl/bin/f90 > checking for math library > checking for -lc... (cached) yes > checking for ar... (cached) ar > checking for ranlib... (cached) ranlib > checking for stdlib.h... (cached) yes > checking for sys/types.h... (cached) yes > checking for strerror... (cached) yes > checking for ftruncate... (cached) yes > checking for st_blksize in struct stat... (cached) yes > checking whether cross-compiling... (cached) no > checking for IEEE floating point format... yes > checking for ANSI C header files... (cached) yes > checking for size_t... (cached) yes > checking for off_t... (cached) yes > checking for ssize_t... (cached) yes > checking for ptrdiff_t... (cached) yes > checking for uchar... (cached) yes > checking whether char is unsigned... (cached) yes > checking whether byte ordering is bigendian... (cached) yes > checking size of short... (cached) 8 > checking size of int... (cached) 8 > checking size of long... (cached) 8 > checking size of float... (cached) 8 > checking size of double... (cached) 8 > checking size of off_t... (cached) 8 > checking size of size_t... (cached) 8 > checking for catman... no > checking for makewhatis... no > checking for manual-page index command... > checking binary distribution directory... > /home/ftp/pub/binary/dummy_system > creating ./config.status > creating macros.make > sed: 28: conftest.subs: invalid command code F Oh oh. I don't like the last line above. It *might* be due to your problem with the Fortran compiler. I hope so. > udcreating fortran/nfconfig.inc > fortran/nfconfig.inc is unchanged > creating libsrc/ncconfig.h > libsrc/ncconfig.h is unchanged > > -- > ____________________________________________________________________ > Curtis Williams, B.S.E.E. > HPC Consultant (619) 822-0017 (voice) > San Diego Supercomputer Center (619) 534-5117 (fax) > P.O. Box 85608 address@hidden > San Diego, CA 92186-5608 http://www.sdsc.edu/~cdub > ____________________________________________________________________ When re-executing the configure script, make sure that you remove the file "config.cache" first. Otherwise, you'll wind up with some definitions that the configure script cached in a previous execution. -------- Steve Emmerson <http://www.unidata.ucar.edu>