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

[Support #GHO-258559]: udunits installation 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: [Support #GHO-258559]: udunits installation problem
  • Date: Wed, 09 Aug 2006 12:23:23 -0600
Art,

> Made it a bit farther. Now the link fails. Relevant files attached. Fille
> "typed_commands" shows which environment variables I set prior to make.
> Yes, I did totally clean (make distclean) before remaking.
> Thanks, Art


The udunits(3) library and udunits(1) utility built OK but the Perl
extension module didn't.  It could be that the perl(1) utility was
built using an incompatible compiler or compiler options than what
was used to build the udunits(3) library.  You can can what compiler
and options were used to build the perl(1) utility via the command

    perl -V

If you don't need the perl(1) extension module for UDUNITS, then I
recommend reconfiguring the build so that it won't build the perl(1)
extension module.  This is done by setting the environment variable
PERL to the empty string before executing the configure script, e.g.,

    $ make distclean
    ...
    $ PERL= ./configure >configure.log 2>&1
    $ make >make.log 2>&1
    ...

FWIW, I'm reflooring my home.  Is that vacation?  :-)


Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: GHO-258559
Department: Support UDUNITS
Priority: High
Status: Closed