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

[Support #WJW-509399]: udunits: fails fortran compile on FC5


> gmake[1]: Entering directory `/home/local/src/udunits-1.12.4/src/lib'
> c89 -c -g -O2 -I../port/misc -I../port/cfortran
> -DUT_DEFAULT_PATH='"/home/local/etc/udunits.dat"'  utlib.c
> In file included from utlib.c:29:
> ../port/cfortran/cfortran.h:132:3: error: #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     -
> Absoft Pro Fortran: Use #define AbsoftProFortran     - Portland Group
> Fortran: Use #define pgiFortran"
> gmake[1]: *** [utlib.o] Error 1
> gmake[1]: Leaving directory `/home/local/src/udunits-1.12.4/src/lib'
> gmake: *** [lib/all] Error 1

The above means that the configure(1) script wasn't told what argument-passing 
conventions to use when compiling C functions that are callable from Fortran 
routines.  Please try the following:

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

    2.  Execute the command "make distclean".

    3.  Ensure that the environment variable CPPFLAGS contains the string 
        (or whatever macro definition is appropriate for your Fortran 
compiler), e.g.,

            CPPFLAGS=-Df2cFortran; export CPPFLAGS

    4.  Execute the command "make".  Redirect both the standard output and 
standard error streams to the file "make.log".

    5.  Execute the command "make test".  Redirect both the standard output and 
standard error streams to the file "test.log".

    6.  Execute the command "make install".  Redirect both the standard output 
and standard error streams to the file "install.log".

Steve Emmerson

Ticket Details
Ticket ID: WJW-509399
Department: Support UDUNITS
Priority: Normal
Status: Closed

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.