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

20040122: UDUNITS build under Linux


> 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

    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 
    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

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

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

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

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

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.