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

[UDUNITS #IDZ-795331]: udunits problem

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 #IDZ-795331]: udunits problem
  • Date: Sat, 24 Mar 2007 15:39:57 -0600
Gary,

> When I use "ar":
> discover01 314% ar -t /usr/local/other/udunits/1.12.4/lib/libudunits.a
> utlib.o
> utparse.o
> utscan.o
> udalloc.o
> 
> When I use "nm":
> discover01 313% nm /usr/local/other/udunits/1.12.4/lib/libudunits.a
> nm: utlib.o: Bad value
> nm: utparse.o: Bad value
> nm: utscan.o: Bad value
> nm: udalloc.o: Bad value
> 
> So it looks like the library is bad for some reason??

Yes.  The object modules in the library are bad.

Could it be that you compiled them in some mode (e.g., 64-bit
mode) but the "nm" utility is 32-bit mode?

Do you still have the file "make.log", which is described in the
file INSTALL in the top-level source-directory of the package?
If so, would you please send it to me.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: IDZ-795331
Department: Support UDUNITS
Priority: Normal
Status: On Hold