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.
Serkan,
Please disregard my previous reply. Your subsequent email indicated the
problem.
(Aside: your email was formatted strangely.)
>Date: Wed, 7 Apr 2004 01:35:16 -0700 (PDT)
>From: serkan eminoglu <address@hidden>
>Organization: ?
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20040406: UDUNITS installation problem on Suse 8.2
>Keywords: 200404060831.i368VOCT023215
The above message contained the following:
> making `all' in directory
> /home/ldm/udunits/src/udunits
>
> make[1]: Entering directory
> `/home/ldm/udunits-1.11.7/src/udunits'
> make[2]: Entering directory
> `/home/ldm/udunits-1.11.7/src/udunits'
> gcc -c -O -I../lib -I../port/misc -DNDEBUG
> -DpgiFortran udunits.c
> gcc -o udunits -O udunits.o
> -L/home/ldm/udunits/src/lib -ludunits -L/home/ldm/ud
> units/src/port/misc -ludport
> /home/ldm/udunits/src/lib/libudunits.a(utlib.o)(.text+0xbff):
> In function `utRai se':
> : undefined reference to `pow'
> /home/ldm/udunits/src/lib/libudunits.a(utlib.o)(.text+0x1607):
> In function `utPr int':
> : undefined reference to `log10'
> collect2: ld returned 1 exit status
> make[2]: *** [udunits] Error 1
> make[2]: Leaving directory
> `/home/ldm/udunits-1.11.7/src/udunits'
> make[1]: *** [program] Error 2
> make[1]: Leaving directory
> `/home/ldm/udunits-1.11.7/src/udunits'
> make: *** [udunits/all] Error 1
It appears that your gcc(1) installation doesn't automatically supply
the Standard C math functions pow(3) and log10(3). This is incorrect
behavior and indicates an improper gcc(1) installation.
You'll either have to correct the gcc(1) installation or locate
those functions. If you do locate them, then add a reference to the
containing library to the LIBS environment variable before (re)executing
the "configure" script. For example, from the top-level
source-directory:
make distclean
export LIBS='-L/opt/gnu/gcc3/lib/libm.a -lm' # example
export ... # additional settings
./configure >configure.log 2>&1
less configure.log
make >make.log 2>&1
less make.log
make test >test.log 2>&1
less test.log
make install >install.log 2>&1
less install.log
make clean
Regards,
Steve Emmerson