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

20040122: UDUNITS build under Linux

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: 20040122: UDUNITS build under Linux
  • Date: Thu, 22 Jan 2004 10:31:25 -0700
John,

> To: address@hidden
> From: John Evans <address@hidden>
> Subject: issues with building udunits
> Organization: USGS
> Keywords: 200401221505.i0MF5Rp2014284 UDUNITS

The above message contained the following:

> Hi,  I had problems building udunits on my linux box.  Items A-F as
> asked for are following.  I was able to get it to compile successfully
> and install, but had to modify
> ${SRC_DIR}/src/udunits-1.11.7/udunits/Makefile line 15 from 
> 
>       ld_math     = 
> 
> to
> 
>       ld_math     = -lm
> 
> Setting LIBS=-lm didn't seem to help.

I tried to determine why you encountered this problem but I was unable
to decode the "configure.log" file that you sent.  It appears that you
sent me the file "config.log" rather than the file "configure.log" and
that the output of the "configure" script was redirected to this file.
Because the file "config.log" is directly written to by the "configure"
script, the result was a difficult-to-decipher jumble of output.  For
example:

    creating cache ./config.cache
    checking type of operating system... linux
    checking for manual-page index command... 
    checking foconfigure:1105: gcc -E -Df2cFortran conftest.c >/dev/null 
2>conftest.out
    configure:1146: gcc -E -Df2cFortran conftest.c >/dev/null 2>conftest.out
    configure:1175: gcc -c  -Df2cFortran coyes

The "creating" and "checking" strings above came from the standard
output of the configure script.  The strings with the numeric line
numbers (e.g., ":1105") come from the configure script writing to the
file "config.log".  Note how the messages are intertwined.

If you'd like to help me uncover the problem, would you please do the
following:

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

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

    3.  Execute the configure script, redirecting both standard output
        and standard error to the file "configure.log" (and not
        "config.log").

    4.  Send me the files "configure.log" and "config.log".

Regards,
Steve Emmerson