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

20021011: building UDUNITS: omitting the perl interface

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: 20021011: building UDUNITS: omitting the perl interface
  • Date: Fri, 11 Oct 2002 10:43:23 -0600
Nguyen Dang Quang,

>Date: Fri, 11 Oct 2002 09:36:34 +0200 (MET DST)
>From: "Nguyen Dang Quang" <address@hidden>
>Organization: ICTP, Italy
>To: address@hidden
>Subject: Re: 20021010: building UDUNITS: omitting the perl interface

The above message contained the following:

> In my network, in ICTP, also had perl : /usr/bin/perl.
> But I can not edit "setenv PERL" in my .cshrc file because my machine is not
> admin. machine; so I didnt see it ( setenv PERL ....)
> How can I resolve this problem?

You should be able to set the PERL environment variable to the empty
string by executing the following command:

    setenv PERL ''

You can test this by executing the following command:

    echo $PERL

It should echo nothing.

Then, execute the command "make distclean" and then execute the configure
script.

Regards,
Steve Emmerson   <http://www.unidata.ucar.edu>