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

Re: 20051114: netcdf-perl-1.2.3



Mark,

>Date: Tue, 15 Nov 2005 13:12:02 -0700
>From: Mark Seefeldt <address@hidden>
>Organization: University of Colorado
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20051114: netcdf-perl-1.2.3

The above message contained the following:

> Thank you for the solution to my installation of netcdf-perl-1.2.3. 
> With the tips that you provided I was able to complete the installation 
> without any errors.
> 
> Unfortunately, I have now hit a snag with the installation of UDUNITS (I 
> am working towards the NetCDF decoders).  I was able to complete the 
> configure and make steps, without errors, and then I came across an 
> error with 'make test'.  I have attached the configure.log, make.log, 
> and test.log output files.
> 
> This is being done on the same RHEL4 Linux workstation.

The "make" output had the following error:

[snip]
> making `all' in directory /usr/local/udunits-1.12.4/src/lib
> 
> make[1]: Entering directory `/usr/local/udunits-1.12.4/src/lib'
> ln -s ../port/misc/udalloc.c .
> ln -s ../port/misc/udalloc.h .
> c89 -c -g -O2 -I../port/misc -I../port/cfortran -DUT_DEFAULT_PATH=3D'"/us=
> r/local/udunits-1.12.4/etc/udunits.dat"'  utlib.c
> In file included from utlib.c:29:
> =2E./port/cfortran/cfortran.h:132:3: #error "cfortran.h:  Can't find your=
>  environment among:    - MIPS cc and f77 2.0. (e.g. Silicon Graphics, DEC=
> stations, ...)         - IBM AIX XL C and FORTRAN Compiler/6000 Version 0=
> 1.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 Ve=
> rsion 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.0=
> 8.07 A 9000/730        - LynxOS: cc or gcc with f2c.                     =
>                        - VAXUltrix: vcc,cc or gcc with f2c. gcc or cc wit=
> h f77.                 -            f77 with vcc works; but missing link =
> magic for f77 I/O.     -            NO fort. None of gcc, cc or vcc gener=
> ate required names.    - f2c    : Use #define    f2cFortran, or cc -Df2cF=
> ortran                 - NAG f90: Use #define NAGf90Fortran, or cc -DNAGf=
> 90Fortran              - Absoft UNIX F77: Use #define AbsoftUNIXFortran o=
> r cc -DAbsoftUNIXFortran     - Absoft Pro Fortran: Use #define AbsoftProF=
> ortran     - Portland Group Fortran: Use #define pgiFortran"
> In file included from utlib.c:1127:
> utlib.c: In function `utInit':
> utlib.c:1051: warning: passing arg 1 of `ReadUnits' discards qualifiers f=
> rom pointer target type
> make[1]: *** [utlib.o] Error 1
> make[1]: Leaving directory `/usr/local/udunits-1.12.4/src/lib'
> make: *** [lib/all] Error 1

This means that the CPPFLAGS environment variable will have to define a
particular C macro in order to tell the C compiler what type of Fortran
interface to use.

Please try the following:

    1.  Go to the top-level source-directory.

    2.  Execute the following commands:

            make distclean
            CC=c89 CFLAGS=-O2 CPPFLAGS=-DpgiFortran \
                ./configure >configure.log 2>&1 &&
            make >make.log 2>&1 &&
            make test >test.log 2>&1 &&
            make install >install.log 2>&1 &&
            echo OK

Regards,
Steve Emmerson


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.