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.
Andres, > Hello again again, :) jaja, the make.log is attached. (Note: I execute this > command, i think that this is what you want 'make > make.log 2>&1' . > Cheers. ... making `dynamic' in directory /home/ldm/UDUNITS/udunits-1.12.4/src/perl /usr/bin/perl /usr/perl5/5.8.4/lib/ExtUtils/xsubpp -typemap /usr/perl5/5.8.4/lib/ExtUtils/typemap -typemap typemap UDUNITS.xs > UDUNITS.xsc && mv UDUNITS.xsc UDUNITS.c Please specify prototyping behavior for UDUNITS.xs (see perlxs manual) gcc -c -I../lib -I../port/misc -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -xarch=v8 -D_TS_ERRNO -xO3 -xspace -xildoff -DVERSION=\"1.12.4\" -DXS_VERSION=\"1.12.4\" -KPIC "-I/usr/perl5/5.8.4/lib/sun4-solaris-64int/CORE" UDUNITS.c gcc: unrecognized option `-KPIC' gcc: language ildoff not recognized gcc: UDUNITS.c: linker input file unused because linking not done Running Mkbootstrap for UDUNITS () chmod 644 UDUNITS.bs rm -f blib/arch/auto/UDUNITS/UDUNITS.so LD_RUN_PATH="" cc -G UDUNITS.o -o blib/arch/auto/UDUNITS/UDUNITS.so -L/home/ldm/UDUNITS/udunits-1.12.4/src/perl/../lib -ludunits -lm sh: cc: not found *** Error code 1 make: Fatal error: Command failed for target `blib/arch/auto/UDUNITS/UDUNITS.so' Current working directory /home/ldm/UDUNITS/udunits-1.12.4/src/perl *** Error code 1 The following command caused the error: dir=`echo perl/dynamic | sed 's,/.*,,'`; \ target=`echo perl/dynamic | sed "s,$dir/,,"`; \ cd $dir && \ echo "making \`$target' in directory `pwd`" && \ echo "" && \ make \ prefix=/home/ldm/UDUNITS/udunits-1.12.4 exec_prefix=/home/ldm/UDUNITS/udunits-1.12.4 \ $target || exit 1 make: Fatal error: Command failed for target `perl/dynamic' I suspect that the compiler used to build your perl(1) installation is not compatible with the compiler you're using to build the perl(1) extension module for UDUNITS. Unfortunately, the same compiler must be used for both. This restriction is imposed by perl(1) and not by the UDUNITS package. Do you want the perl(1) extension module for UDUNITS? If not, then you can cause the build procedure to ignore it by setting the environment variabe PERL to the empty string before executing the configure(1) script (remember to execute the command "make distclean" first). You can discover what C compiler was used to build your perl(1) installation via the command "perl -V". If it indicates that, for example, the SUN cc(1) compiler was used to build perl(1), then you will have to use that compiler to build the UDUNITS package with the perl(1) extension module. This can be done by setting the environment variable CC to the pathname of the same C compiler that was used to build your perl(1) installation and then re-executing the configure(1) script after first executing the command "make distclean". Regards, Steve Emmerson Ticket Details =================== Ticket ID: NWU-852580 Department: Support UDUNITS Priority: Normal Status: Closed