HP-UX and shared libraries

[Andrew M. Ochsner]

Hi.  My name is Andy Ochsner.  I am an intern at HP.  I just ported
KDE to HP-UX 11.00.  I was hoping to be able to distribute the
binaries (in addition to source code), but there is one little problem.
 A make clean destroys my installation.  The problem is that many of the
shared libraries have statically hardcoded into them other libraries
they depend on, and refer to the versions that are in .libs
directories.  See example below:

hpadl843:~/kde2-aCC/lib> chatr libkdecore.sl
libkdecore.sl:
         shared library
         shared library dynamic path search:
             SHLIB_PATH     enabled   second
             embedded path  enabled   first  /home/aochsner/kde2-aCC/lib

         internal name:
             libkdecore.sl.3
         shared library list:
             dynamic   /usr/lib/libXext.3
             static
/home/aochsner/src/kde-aCC/kdelibs-2.2/kdecore/../dcop/.libs/libDCOP.sl.1

             dynamic   /usr/lib/libc.2
         shared vtable support disabled
         static branch prediction disabled
         executable from stack: D (default)
         kernel assisted branch prediction enabled
         lazy swap allocation disabled
         text segment locking disabled
         data segment locking disabled
         third quadrant private data space disabled
         fourth quadrant private data space disabled
         data page size: D (default)
         instruction page size: D (default)
         nulptr references disabled

The fact that it's statically hardcoded in there means I can't do a
lookup according to SHLIB_PATH or the embedded path.  The executables
are fine.  They get relinked at installation time, so they have the
correct dependencies.  But libraries are not relinked, therefore, they
still have these bad dependancies.  Is there any way to make libtool "do
the right thing" or just an easy workaroud?  Remember, there are 100
some libraries that this affects, so manually changing things isn't a
good option.   Any help would be tremendous.  I don't forsee being able
to distribute my entire build environment to people who might want this.

Thanks
Andy O