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.
Kenneth, Your "configure.log" file didn't indicate any problems. You should be able to execute the commands "make", "make install", and "make install_setuids" (as root) without any problems. Please be sure to read and follow the installation and configuration instructions at http://my.unidata.ucar.edu/content/software/ldm/ldm-6.3.0/basics/index.html#installation Contact me if you encounter a problem. Regards, Steve Emmerson LDM Developer NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us. ------- Original Message >To: <address@hidden> >From: "Scheeringa, Kenneth L" <address@hidden> >Subject: LDM install question >Organization: UCAR/Unidata >Keywords: 200503211935.j2LJZlv2005091 This is a multi-part message in MIME format. Hello LDM support, I am rebuilding the Unidata LDM software from our (recently deceased) AIX system to a new Linux box we just purchased running RedHat WS3 (on Dell). I have downloaded the LDM 6.3.0 distribution from your web site and am now on the configure step in the install process. With my limited Unix install experience, I do not know if error messages logged during the configure process are critical or not to prevent proceeding to the next step. I have enclosed my configure.log and config.log Can you please browse these log files and see if critical errors have occurred and if so, what I need to do to work around them? I really appreciate your help! [snip] checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /usr/bin/gcc accepts -g... yes checking for /usr/bin/gcc option to accept ANSI C... none needed checking the C compiler... works configure: Checking how to maximize the (long, void*, off_t) programming environment checking if the system supports _XBS5_LPBIG_OFFBIG... no checking if the system supports _XBS5_ILP32_OFFBIG... yes configure: -D_MAPRGNS configure: cflags="-D_FILE_OFFSET_BITS=64" configure: ldflags="" configure: libs="" configure: ARFLAGS="-cru" checking the C compiler (again)... works checking the installation prefix... /usr/local/ldm/ldm-6.3.0 checking domain name... agry.purdue.edu checking how to run the C preprocessor... /usr/bin/gcc -E checking for egrep... grep -E checking for HP-UX... no checking the C preprocessor... works checking for ar... ar checking for perl... /usr/bin/perl checking for POSIX shell... /bin/sh checking for yacc... yacc checking for ranlib... ranlib checking mmap()... yes checking LDMHOME... /usr/local/ldm checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for int... yes checking size of int... 4 checking for long... yes checking size of long... 4 checking for size_t... yes checking for off_t... yes checking for ssize_t... yes checking for ptrdiff_t... yes checking for socklen_t... yes checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for fsync... yes checking for ftruncate... yes checking for memmove... yes checking for memcmp... yes checking for rename... yes checking for strerror... yes checking for waitpid... yes checking for strdup... yes checking for seteuid... yes checking for setenv... yes checking for mmap... yes checking for sig_atomic_t in signal.h... defined checking for an ANSI C-conforming const... yes checking for struct stat.st_blksize... yes checking for sigaction... yes checking networking references... checking ulog defines... -DNO_REPLACE_SYSLOG -DULOGNAME=/dev/log -DLOGNAME_ISSOCK checking for gdbm_open in -lgdbm... yes checking gdbm.h usability... yes checking gdbm.h presence... yes checking for gdbm.h... yes checking for manual-page index command... configure: creating ./config.status config.status: creating macros.make config.status: creating pqbinstats/mailpqstats config.status: creating scour/scour config.status: creating scripts/ldmadmin config.status: creating scripts/ldmadmin-pl.conf config.status: creating scripts/ldmprods config.status: creating scripts/ldmfail config.status: creating scripts/netcheck config.status: creating scripts/syscheck config.status: creating scripts/ldmcheck config.status: creating config/ldmconfig.h configure: configuring in rpc configure: running /bin/sh './configure' --prefix=/usr/local/ldm/ldm-6.3.0 'CC=/usr/bin/gcc' --cache-file=/dev/null --srcdir=. checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /usr/bin/gcc accepts -g... yes checking for /usr/bin/gcc option to accept ANSI C... none needed checking the C compiler... works configure: Checking how to maximize the (long, void*, off_t) programming environment checking if the system supports _XBS5_LPBIG_OFFBIG... no checking if the system supports _XBS5_ILP32_OFFBIG... yes configure: -D_MAPRGNS configure: cflags="-D_FILE_OFFSET_BITS=64" configure: ldflags="" configure: libs="" configure: ARFLAGS="-cru" checking the C compiler (again)... works checking for ranlib... ranlib checking whether byte ordering is bigendian... no checking how to run the C preprocessor... /usr/bin/gcc -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for short... yes checking size of short... 2 checking for int... yes checking size of int... 4 checking for long... yes checking size of long... 4 checking for float... yes checking size of float... 4 checking for double... yes checking size of double... 8 checking size of enum... 4 checking size of gid_t... 4 checking stropts.h usability... yes checking stropts.h presence... yes checking for stropts.h... yes configure: creating ./config.status config.status: creating Makefile config.status: creating config.h ~~~~~~~~~~~~~~~~~~~~~~~~ Ken Scheeringa Assistant State Climatologist Indiana State Climate Office (iSCLIM) Agronomy Dept. Purdue University ------- End of Original Message