[Paraview] mysterious error when using dpkg-mkdeb

[Cook, Rich]

Hello, wizards and keepers of deep Paraview wisdom:

For some reason, on our RHEL 6 clusters, during a normal build, I see this: 
-- Looking for shl_load in dld;dl
-- Looking for shl_load in dld;dl - not found

However, trying to package our paraview install process in a dpkg, I see this during the cmake process: 
-- Looking for shl_load in dld;dl
-- Looking for shl_load in dld;dl - found

Because of that, later in the log, the following happens about 3% into the build:
 
cd /tmp/dpkg-mkdeb.HqY7g9wWL0/src/ParaView-3.14.0-Build/VTK/Utilities/vtklibxml2 && /usr/local/tools/cmake-2.8.7/bin/cmake -E cmake_link_script CMakeFiles/vtklibxml2.dir/link.txt --verbose=1
/usr/local/tools/openmpi-gnu-debug-1.4.3/bin/mpicc  -fPIC   -I/usr/gapps/visit/mili/1.10.0/linux-x86_64_gcc-4.1/include -I/usr/gapps/visit/hdf5/1.8.4/linux-x86_64_gcc-4.1/include  -I/usr/local/tools/openmpi-gnu-debug-1.4.3/include  -w -g    -shared -Wl,-soname,libvtklibxml2.so.pv3.14 -o ../../../bin/libvtklibxml2.so.pv3.14 CMakeFiles/vtklibxml2.dir/DOCBparser.c.o CMakeFiles/vtklibxml2.dir/HTMLparser.c.o CMakeFiles/vtklibxml2.dir/HTMLtree.c.o CMakeFiles/vtklibxml2.dir/SAX.c.o CMakeFiles/vtklibxml2.dir/SAX2.c.o CMakeFiles/vtklibxml2.dir/c14n.c.o CMakeFiles/vtklibxml2.dir/catalog.c.o CMakeFiles/vtklibxml2.dir/chvalid.c.o CMakeFiles/vtklibxml2.dir/debugXML.c.o CMakeFiles/vtklibxml2.dir/dict.c.o CMakeFiles/vtklibxml2.dir/encoding.c.o CMakeFiles/vtklibxml2.dir/entities.c.o CMakeFiles/vtklibxml2.dir/error.c.o CMakeFiles/vtklibxml2.dir/globals.c.o CMakeFiles/vtklibxml2.dir/hash.c.o CMakeFiles/vtklibxml2.dir/legacy.c.o CMakeFiles/vtklibxml2.dir/list.c.o CMakeFiles/vtklibxml2.dir/nanoftp.c.o CMakeFiles/vtklibxml2.dir/nanohttp.c.o CMakeFiles/vtklibxml2.dir/parser.c.o CMakeFiles/vtklibxml2.dir/parserInternals.c.o CMakeFiles/vtklibxml2.dir/pattern.c.o CMakeFiles/vtklibxml2.dir/relaxng.c.o CMakeFiles/vtklibxml2.dir/schematron.c.o CMakeFiles/vtklibxml2.dir/threads.c.o CMakeFiles/vtklibxml2.dir/tree.c.o CMakeFiles/vtklibxml2.dir/uri.c.o CMakeFiles/vtklibxml2.dir/valid.c.o CMakeFiles/vtklibxml2.dir/xinclude.c.o CMakeFiles/vtklibxml2.dir/xlink.c.o CMakeFiles/vtklibxml2.dir/xmlIO.c.o CMakeFiles/vtklibxml2.dir/xmlmemory.c.o CMakeFiles/vtklibxml2.dir/xmlmodule.c.o CMakeFiles/vtklibxml2.dir/xmlreader.c.o CMakeFiles/vtklibxml2.dir/xmlregexp.c.o CMakeFiles/vtklibxml2.dir/xmlsave.c.o CMakeFiles/vtklibxml2.dir/xmlschemas.c.o CMakeFiles/vtklibxml2.dir/xmlschemastypes.c.o CMakeFiles/vtklibxml2.dir/xmlstring.c.o CMakeFiles/vtklibxml2.dir/xmlunicode.c.o CMakeFiles/vtklibxml2.dir/xmlwriter.c.o CMakeFiles/vtklibxml2.dir/xpath.c.o CMakeFiles/vtklibxml2.dir/xpointer.c.o ../../../bin/libvtkzlib.so.pv3.14 -ldl -ldld -lpthread -ldl -lm -ldld -lpthread -lm -Wl,-rpath,/tmp/dpkg-mkdeb.HqY7g9wWL0/src/ParaView-3.14.0-Build/bin: 
/usr/bin/ld: cannot find -ldld
collect2: ld returned 1 exit status

Curiously, it does not stop there but waits until 26% of the way through before erroring out. 
And it all comes back to this line in the ParaView-3.14.0-Source/VTK/Utilities/vtklibxml2/CMakeLists.txt file: 

CHECK_LIBRARY_EXISTS_CONCAT("dld"      shl_load       HAVE_SHLLOAD)

I have commented out that line and hope to come back in the morning learning that I succeeded.  So far, so good, the offending library compiled this time.  :-)  What I'm wondering is, how can I figure out what's different in my mkdeb world, and how can I make the build successful without hacking into low level source files like this?  

Thanks! 

Logfiles available upon request.

-- 
✐Richard Cook   
✇ Lawrence Livermore National Laboratory
Bldg-453 Rm-4024, Mail Stop L-557        
7000 East Avenue,  Livermore, CA, 94550, USA
☎ (office) (925) 423-9605    
☎ (fax) (925) 423-6961
---
Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept.
(opinions expressed herein are mine and not those of LLNL)