> X-Original-To: ksh93-integration-discuss at opensolaris.org
> Delivered-To: ksh93-integration-discuss at opensolaris.org
> Subject: Re: [ksh93-integration-discuss] Re: proposed solution        for 
LD_LIBRARY_PATH problem
> From: Bill Sommerfeld <sommerfeld at sun.com>
> To: Korn Shell 93 integration/migration project discussion 
<ksh93-integration-discuss at opensolaris.org>
> Date: Wed, 06 Dec 2006 19:31:38 -0500
> Mime-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Cc: gk at onnv.eng.sun.com
> X-BeenThere: ksh93-integration-discuss at opensolaris.org
> X-Mailman-Version: 2.1.4
> List-Id: Korn Shell 93 integration/migration project discussion 
<ksh93-integration-discuss.opensolaris.org>
> List-Unsubscribe: 
<http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss>, 
<mailto:ksh93-integration-discuss-request at 
opensolaris.org?subject=unsubscribe>
> List-Archive: 
<http://mail.opensolaris.org/pipermail/ksh93-integration-discuss>
> List-Post: <mailto:ksh93-integration-discuss at opensolaris.org>
> List-Help: 
<mailto:ksh93-integration-discuss-request at opensolaris.org?subject=help>
> List-Subscribe: 
<http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss>, 
<mailto:ksh93-integration-discuss-request at opensolaris.org?subject=subscribe>
> 
> On Wed, 2006-12-06 at 16:36 -0500, James Carlson wrote:
> > The AT&T library in question will have been built against the proto
> > area's header files.  Thus, if someone decides that we need to change
> > the signature of a function (using redefine_extname and a #define),
> > we'll end up with inadvertent references from the newly-built AT&T
> > library to the not-yet-existent redefined symbol.  Perhaps unlikely,
> > but not impossible.
> > 
> > I think using LD_LIBRARY_PATH (or, for that matter, LD_PRELOAD) as any
> > part of the build process ought to be avoided.  We go to great lengths
> > elsewhere to make sure that the few bits that must be run on the build
> > machine are built correctly -- not using the proto area at all.
> 
> Sounds like libpp and the tools which invoke it ought to be built as
> host code out of usr/src/tools (and packaged into /opt/onbld for those
> not using nightly -t). 
> 
>                                               - Bill
> 

We considered putting the tools and library (libpp) into the SUNWonbld 
package, to install into /opt/onbld, but libpp has a dependency on
/usr/lib/libast.so.1, another new AT&T library also needed by ksh93.  
Segregating libpp into the SUNWonbld package could lead to
possible problems if libpp is not kept up to date with libast.

        April





Reply via email to