[ksh93-integration-discuss] Re: proposed solution for LD_LIBRARY_PATH problem

[Danek Duvall]

On Wed, Dec 06, 2006 at 12:50:52PM -0800, April Chin wrote:

> For building l10n messages for the ksh93 project, we need to use ksh93 itself 
> and the AT&T libraries it uses--libast, libshell, libcmd, and libdll.  
> This process also requires using another AT&T library, 
> libpp, which will not be part of the Solaris release, although
> it has dependencies on (and should probably be kept in sync with) libast.

Ah.  This last was not something I was aware of.  Can you explain what this
library is and why it won't be delivered?

> After some discussion, we'd like to build the message files by
> pointing LD_LIBRARY_PATH at a newly-created temporary directory 
> under $(TMPDIR) (or /tmp by default) which would contain symlinks 
> to the needed AT&T libraries in the proto area and a symlink to the 
> newly-built libpp in $(SRCDIR)/usr/lib/libpp/$(MACH)/libpp.so.1.  

This would certainly be safer than using $ROOT, but the problem doesn't
entirely disappear -- if there are any interfaces between the AT&T
libraries and libc (and any other libraries loaded by running ksh93) which
have changed incompatibly.  Could that ever happen?

Danek