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.
Scott, > I'm building ldm 6.7.0 on an RHEL5 box, and got the following error: > > make[2]: Entering directory `/usr/local/ldm/ldm-6.7.0/src/pqcheck' > /usr/bin/gcc -c -O -m64 -DNDEBUG -I.. -I../config -I../misc -I../ulog > -I../protocol -I../pq pqcheck.c > pqcheck.c: In function `main': > pqcheck.c:174: error: `LOG_LDM0' undeclared (first use in this function) > pqcheck.c:174: error: (Each undeclared identifier is reported only once > pqcheck.c:174: error: for each function it appears in.) > make[2]: *** [pqcheck.o] Error 1 > make[2]: Leaving directory `/usr/local/ldm/ldm-6.7.0/src/pqcheck' > make[1]: *** [subdir_target] Error 1 > make[1]: Leaving directory `/usr/local/ldm/ldm-6.7.0/src' > make: *** [pqcheck/all] Error 2 > > > If I change my configure line to exclude the --enable-logging option > (I had set it to ldm0) and let it default to local0, everything seems > to build fine. I suspect you invoked the "configure" script with the argument "--enable-logging=ldm0". Unfortunately, there is no "LDM0" facility as far as the system logging daemon is concerned. The only viable possibilities are "local0", "local1", ... "local9". Using the default "local0" should work as long as that facility isn't being used by anything else in the system logging configuration file (etc/syslogd.conf). > Scott Brunza > > > --- Let us all bask in television's warm glowing warming glow --- > Scott Brunza 860.326.3637 address@hidden Regards, Steve Emmerson Ticket Details =================== Ticket ID: OBQ-956697 Department: Support LDM Priority: Normal Status: Closed