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

[UDUNITS #LFG-950358]: problem compiling on Mac OS X 10.4

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.

  • Subject: [UDUNITS #LFG-950358]: problem compiling on Mac OS X 10.4
  • Date: Mon, 02 Jul 2007 13:56:51 -0600
John,

> I'm having trouble compiling v.1.2.4 on a Mac (10.4.10) using
> gfortran.  Here's the version info for the compiler:
> 
> gfortran -v
> Using built-in specs.
> Target: powerpc-apple-darwin8.9.0
> Configured with: ../gcc-4.3-20070511/configure --enable-
> languages=fortran --enable-static --disable-shared
> Thread model: posix
> gcc version 4.3.0 20070511 (experimental)
> 
> I've set:
> FC=/usr/local/bin/gfortran
> FF=-O
> 
> 
> Listed below is the error.  Can anyone help me?
> 
> Thanks!
> 
> --john
> 
> ...
> 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
...

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 "-Df2cFortran" (or whatever macro definition is
        appropriate for your Fortran compiler), e.g.,

            CPPFLAGS=-Df2cFortran; export CPPFLAGS

        The set of potential macros can be found in the examples of
        the file INSTALL in the top-level source-directory.

    4.  Execute the "configure" script.  Redirect both the
        standard output and standard error streams to the file
        "configure.log".

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

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

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

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: LFG-950358
Department: Support UDUNITS
Priority: Normal
Status: Closed