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.
Jay, > Here's the output: > linux-vdso.so.1 => (0x00007fff52fff000) > libldm.so.0 => /usr/local/ldm/ldm-6.11.2/src/lib/.libs/libldm.so.0 > (0x00007f04acddf000) > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 > (0x00007f04acbb9000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f04ac7fa000) > /lib64/ld-linux-x86-64.so.2 (0x00007f04ace4b000) Wow! I don't know what to tell you. The output from ldd(1) isn't even showing the "libxml2" library. I looked at the output of your "make install" and compared it to mine. The regutil(1) utility was linked correctly against the "libxml2" library. The only thing I can think of is that your development environment (compiler, linker, loader) is messed up somehow. I suggest you show this thread to your systems administrator. Sorry I couldn't be more helpful. > Also, for what it's worth, the GCC compiler version is 4.6.3. I think I > forgot to mention that previously. gcc(1) shouldn't be a problem. > Jay Regards, Steve Emmerson Ticket Details =================== Ticket ID: YVG-914431 Department: Support LDM Priority: Normal Status: Closed