[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 980317: Again netcdf-3.4...
- Subject: Re: 980317: Again netcdf-3.4...
- Date: Tue, 17 Mar 1998 09:38:00 -0700
Guido,
> To: address@hidden
> From: Guido Tesch <address@hidden>
> Subject: Again netcdf-3.4...
> Organization: University of Bonn, Germany
> Keywords: 199803171101.EAA10524
In the above message, you wrote:
> The first time there was a problem with the tar-file. I fixed that one,
> but now I get the following message when make-ing:
>
> /home/tesch/gmt/netcdf-3.4/src > make
> make[1]: Entering directory `/home/tesch/gmt/netcdf-3.4/src'
>
> Making `all' in directory /home/tesch/gmt/netcdf-3.4/src/libsrc
>
> make[2]: Entering directory `/home/tesch/gmt/netcdf-3.4/src/libsrc'
> cc -c -O -I. -DNDEBUG attr.c
> cc -c -O -I. -DNDEBUG dim.c
> cc -c -O -I. -DNDEBUG error.c
> cc -c -O -I. -DNDEBUG -DVERSION=`cat ../VERSION` libvers.c
> cc -c -O -I. -DNDEBUG nc.c
> cc -c -O -I. -DNDEBUG ncio.c
> cc -c -O -I. -DNDEBUG ncx.c
> cc -c -O -I. -DNDEBUG putget.c
> cc -c -O -I. -DNDEBUG string.c
> cc -c -O -I. -DNDEBUG v1hpg.c
> cc -c -O -I. -DNDEBUG v2i.c
> cc -c -O -I. -DNDEBUG var.c
> ar cru libnetcdf.a attr.o dim.o error.o libvers.o nc.o ncio.o ncx.o
> putget.o string.o v1hpg.o v2i.o var.o
> ranlib libnetcdf.a
> make[2]: Leaving directory `/home/tesch/gmt/netcdf-3.4/src/libsrc'
>
> Returning to directory /home/tesch/gmt/netcdf-3.4/src
>
> make[1]: Leaving directory `/home/tesch/gmt/netcdf-3.4/src'
> make[1]: Entering directory `/home/tesch/gmt/netcdf-3.4/src'
>
> Making `all' in directory /home/tesch/gmt/netcdf-3.4/src/fortran
>
> make[2]: Entering directory `/home/tesch/gmt/netcdf-3.4/src/fortran'
> cc -c -O -I../libsrc -DNDEBUG fort-attio.c
> In file included from ncfortran.h:13,
> from fort-attio.c:6:
> cfortran.h:151: #error "cfortran.h: Can't find your environment
> among: - MIPS cc and f77 2.0. (e.g. Silicon Graphics, DECstations,
> ...) - IBM AIX XL C and FORTRAN Compiler/6000 Version
> 01.01.0000.0000 - VAX VMS CC 3.1 and FORTRAN
> 5.4. - Alpha VMS DEC C 1.3 and DEC
> FORTRAN 6.0. - Alpha OSF DEC C and DEC
> Fortran for OSF/1 AXP Version 1.2 - Apollo DomainOS 10.2
> (sys5.3) with f77 10.7 and cc 6.7. -
> CRAY -
> NEC SX-4 SUPER-UX -
> CONVEX -
> Sun -
> PowerStation Fortran with Visual C++ -
> HP9000s300/s700/s800 Latest test with: HP-UX A.08.07 A 9000/730 -
> LynxOS: cc or gcc with f2c. -
> VAXUltrix: vcc,cc or gcc with f2c. gcc or cc with f77.
> - - f77 with vcc works; but missing link magic for f77 I/O.
> - - NO fort. None of gcc, cc or vcc generate required names.
> - - f2c : Use #define f2cFortran, or cc -Df2cFortran
> - - NAG f90: Use #define NAGf90Fortran, or cc -DNAGf90Fortran
> - - Absoft UNIX F77: Use #define AbsoftUNIXFortran or cc
> - -DAbsoftUNIXFortran"
> make[2]: *** [fort-attio.o] Error 1
> make[2]: Leaving directory `/home/tesch/gmt/netcdf-3.4/src/fortran'
> make[1]: *** [subdir_target] Error 1
> make[1]: Leaving directory `/home/tesch/gmt/netcdf-3.4/src'
> make: *** [fortran/all] Error 2
> laptop-zimmer:/home/tesch/gmt/netcdf-3.4/src >
>
> My system is a Red-Hat-Linux ver. 2.0.30. Any ideas?...
>
> Thanks,
>
>
> Guido
> - --
> ////
> 0(o o)0
> - -oOO--(_)--OOo--------------------------------------------------------
> University of Bonn, Germany
> Guido E-Mail: address@hidden
> Tesch URL: http://titan.informatik.uni-bonn.de/~tesch
> Tel.: +49-228-679072
> oooO Presently working at GMD, Sankt Augustin, Germany
> ( ) Oooo http://www.gmd.de/ Tel.: +49-2241-14-2714
> - ---\ (---( )--------------------------------------------------------
> \_) ) /
> (_/
Try the following:
1. Go to the top-level, source directory.
2. Execute the command "make distclean".
3. Remove the file "config.cache" if it exists.
4. Set your environment variables as before.
5. Ensure that the environment variable CFLAGS contains the string
"-Df2cFortran" (this is the key to building on a Linux system).
6. Re-execute the configure script. Redirect its standard output
and standard error to the file "configure.log". If an error
occurs in the output, then stop and send me the file.
7. Re-execute the command "make". Redirect its standard output and
standard error to the file "make.log". If an error occurs in the
output, then stop and send me the file.
8. Continue with the installation as specified in the INSTALL file.
Please let me know if this helps.
--------
Steve Emmerson <http://www.unidata.ucar.edu>