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

20050110: problem building udunits on freebsd 4.7-RELEASE

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: 20050110: problem building udunits on freebsd 4.7-RELEASE
  • Date: Mon, 10 Jan 2005 14:20:57 -0700
Neil,

> To: Unidata Support <address@hidden>
> From: Neil Smith <address@hidden>
> Subject: problem building udunits on freebsd 4.7-RELEASE
> Organization: TAMU
> Keywords: 200501102105.j0AL52v2014190 UDUNITS FreeBSD

The above message contained the following:

> I'm trying to build the newest udunits, 1.12.2, on FreeBSD 4.7-RELEASE
> and can't get the configure to complete.  I'm using the env
> recommended for a FreeBSD 4.8 because I can't locate my notes on my
> build of udunits-1.11.7, which built OK way back when:
> 
> CC=/usr/bin/gcc
> CPPFLAGS=Df2cFortran
> CFLAGS=-O
> PERL=/usr/bin/perl
> FC=g77
> F90=
> FFLAGS=-O
> CXXFLAGS=-O
> CXX=g++

The above should work if you change

    CPPFLAGS=Df2cFortran

to

    CPPFLAGS=-Df2cFortran

To solve the problem of /lib/cpp not working:

> checking the C preprocessor... configure: warning: C preprocessor, 
> `/lib/cpp', doesn't work

set the environment variable CPP to "gcc -E", e.g.,

    export CPP='gcc -E'

> Any help much appreciated.
> -Neil
> ------------------
> Neil R. Smith                         address@hidden
> Comp.Sys.Mngr.                        (979)845-6272
> Dept. Atmospheric Sciences/Texas A&M University

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.