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.
Bob, To install the package on your system, I would use the following settings: CPPFLAGS='-DNDEBUG -Df2cFortran' CC=gcc CFLAGS='-O' (The "-Df2cFortran" is the key) Before executing the configure(1), you may add these definitions to the file CUSTOMIZE in the top-level source-directory or set them as environment variables in the current environment. If you want the perl(1) interface, then set the variable PERL to the pathname of the perl(1) utility; otherwise, define that variable to be the empty string. > Sorry Steve: > > If I had looked at the output from the make -- which I sent previously, > I saw these lines: > > In file included from utlib.c:29: > ../port/cfortran/cfortran.h:133:3: error: #error "cfortran.h: Can't > find your environment among: - MIPS cc and f77 2.0. (e.g. Silicon > Graphics, DECstations, ...) - IBM AIX XL C and FORTRAN > Compiler/6000 Version 01.01.0000.0000 - VAX VMS CC 3.1 and > FORTRAN 5.4. - Alpha VMS DEC C > 1.3 and DEC FORTRAN 6.0. - Alpha OSF DEC > C and DEC Fortran for OSF/1 AXP Version 1.2 - Apollo > DomainOS 10.2 (sys5.3) with f77 10.7 and cc 6.7. - CRAY > - > NEC SX-4 SUPER-UX > - CONVEX > - Sun > - PowerStation Fortran with Visual C++ > - HP9000s300/s700/s800 Latest test with: HP-UX A.08.07 A > 9000/730 - LynxOS: cc or gcc with f2c. > - VAXUltrix: vcc,cc or gcc with f2c. gcc or cc with > f77. - f77 with vcc works; but missing link > magic for f77 I/O. - NO fort. None of gcc, cc or vcc > generate required names. - f2c : Use #define f2cFortran, or > cc -Df2cFortran - NAG f90: Use #define NAGf90Fortran, > or cc -DNAGf90Fortran - Absoft UNIX F77: Use #define > AbsoftUNIXFortran or cc -DAbsoftUNIXFortran - Absoft Pro Fortran: > Use #define AbsoftProFortran - Portland Group Fortran: Use #define > pgiFortran" > > If I was a good sysadmin, I would have read the INSTALL file in the > installation package, but I was a BAD system admin and didn't. I haven't > built software form in a LONG time. It's all "yum install" for me of late. ;-) > > Under tested systems in INSTALL I found this: > > linux_2.4-i686 (Daffy): > CPPFLAGS='-DNDEBUG -Df2cFortran' > CC=/usr/bin/gcc > CFLAGS='-O -fno-builtin' > PERL=/usr/bin/perl > > I probably need to tweak the options, but I'm not sure where > to put these overrides? Or am I completely off base? > > Suggestions? > > -- Bob > > If it helps: We've got GNU Fortran in /usr/bin as gfortran and gcc for the > > Fortran and C/C++ compilers. > > Like I said, it's been so long since I've actually compiled software from > source > like this, I'd forgotten some of the crap that configure tries to figure out > and > some of the ANCIENT platforms they try to support: Ultrix? SunOS? OMG! > > I'll wait till I hear back from Steve. I suspect I just need to tweak > the options > and it will compile cleanly. > > -- Bob Regards, Steve Emmerson Ticket Details =================== Ticket ID: ZTJ-301961 Department: Support UDUNITS Priority: Normal Status: Closed