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.
Manuel, > To: <address@hidden> > From: Manuel Gloor <address@hidden> > Organization: UCAR/Unidata > Keywords: 200205062128.g46LSra03115 The above message contained the following: > Dear Mister, dear Madam, > can you please help me with my problems > installing udunits. Following your > points 1....9 I obtained > the following messages: > on execution of ./configure: > > ./configure: system: not found > > on execution of make: > > Warning: -L../lib changed to > -L/pf/m/m212045/lib/udunits-1.11.7/src/perl/../lib > Please specify prototyping behavior for UDUNITS.xs (see perlxs manual) > cc: Warning: illegal option -fno-strict-aliasing > cc: Warning: illegal option -fPIC > "/sw/s8/perl-5.6.1/lib/5.6.1/sun4-solaris/CORE/iperlsys.h", line 418: > formal parameter lacks name: param #1 > "/sw/s8/perl-5.6.1/lib/5.6.1/sun4-solaris/CORE/iperlsys.h", line 418: > formal parameter lacks name: param #2 > "/sw/s8/perl-5.6.1/lib/5.6.1/sun4-solaris/CORE/iperlsys.h", line 418: > formal parameter lacks name: param #3 > "/sw/s8/perl-5.6.1/lib/5.6.1/sun4-solaris/CORE/iperlsys.h", line 418: > syntax error before or at: __attribute__ > "/sw/s8/perl-5.6.1/lib/5.6.1/sun4-solaris/CORE/iperlsys.h", line 418: > warning: syntax error: empty declaration > "/sw/s8/perl-5.6.1/lib/5.6.1/sun4-solaris/CORE/regexp.h", line 18: cannot > recover from previous errors > cc: acomp failed for UDUNITS.c > gmake-s25[1]: *** [UDUNITS.o] Error 2 > gmake-s25: *** [perl/dynamic] Error 1 I suspect that your perl(1) utility was built using a different compiler than the one you're using to build the UDUNITS package. In general, if you want the perl UDUNITS extension module, then the same compiler must be used to build the module as was used to build the perl utility. You can discover what compiler was used to build the perl utility via the following command: perl -V If I'm correct, then you have several options: 1. If you don't need the perl extension module, then follow steps 3 through 9 near the end of the file INSTALL. At step 5, ensure ththat e PERL environment variable is set to the empty string. 2. If you want the perl extension module, then you must either A. Build a perl utility using the /opt/SUNWspro/bin/cc compiler. or B. Build the UDUNITS package using the same compiler that built the perl utility. To do this, perform steps 3 through 9 near the end of the file INSTALL. At step 5, ensure that the environment variable CC is set to the compiler that built the perl utility. Please let me know if this helps. Regards, Steve Emmerson <http://www.unidata.ucar.edu>