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

Re: 19991004: compiling of UDUNITS



Brian,

>Date: Mon, 4 Oct 1999 12:15:23 -0400 (EDT)
>From: Brian Blanton <address@hidden>
>Organization: University of North Carolina @ Chapel Hill
>To: Steve Emmerson <address@hidden>
>Subject: Re: 19991004: compiling of UDUNITS 
>Keywords: 199910041334.HAA12148

In the above message, you wrote:

> Thanks for the quick response.  We (here in Chapel Hill) were
> relatively unaffected by the hurricane. But east of here is still
> a huge mess.  
> 
> Here's the diagnostic as per above.
> 
> After hitting return  on "make utlib, I get the following:
> gcc -E -I../port/misc -I../port/cfortran 
> -DUT_DEFAULT_PATH='"/root/udunits-1.11.
> 7/etc/udunits.dat"'  utlib.c > utlib.i
> In file included from utlib.c:29:
> ../port/cfortran/cfortran.h:153: #error "cfortran.h:  Can't find your 
> environmen
> t 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"

The above error indicates that your build-environment is left over from
an execution of the configure script in which the environment variable
CPPFLAGS did not contain the string "-DAbsoftProFortran" (and it needs
to).  Do the following to correct the situation:

    1.  Go to the top-level source directory.

    2.  Perform steps 3 through 5 near the end of the INSTALL file.

    3.  Ensure that the environment variable CPPFLAGS contains the
        string "-DAbsoftProFortran" (this is where that C macro should
        be defined: in the environment prior to executing the configure
        script).

    4.  Execute the configure script.  Redirect both standard output and
        standard error to the file "configure.log".  If an error occurs,
        then stop and send me the file "configure.log".

This will get the build environment as it should be.  When you've done
that, then do the following:

    5.  Go into the subdirectory "lib/".

    6.  Remove the file "utlib.i" if it exists.

    7.  Execute the command "make utlib.i".

    8.  Send me the function "utmake" from the file "utlib.i".

    9.  Execute the command "make utlib.o".  Redirect both standard
        output and standard error to the file "utlib.log".  Send me the
        file "utlib.log".

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


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.