Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@stdcxx.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <47DA8BA7.5020109@roguewave.com>
Date: Fri, 14 Mar 2008 08:28:55 -0600
From: Andrew Black <ablack@roguewave.com>
User-Agent: Thunderbird 1.5.0.14 (X11/20060911)
MIME-Version: 1.0
To: dev@stdcxx.apache.org
Subject: Re: STDCXX-488
References: 
 <CFFDD219128FD94FB4F92B99F52D0A49010A364C@exchmail01.Blue.Roguewave.Com>
In-Reply-To: 
 <CFFDD219128FD94FB4F92B99F52D0A49010A364C@exchmail01.Blue.Roguewave.Com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

The failure currently observed is an inability to load the libstd
library in dynamic builds.  When the RPATH makefile variable was
introduced, it was decided that it was a cleaner way to provide the
executables with a location for the library than the alternative.  That
alternative is to have some complex logic to determine whether the path
should be prepended to LD_LIBRARY_PATH, LD_LIBRARY_PATH_64, SHLIBPATH,
DYLDPATH, or some other platform-dependent environment variable.

--Andrew Black

Eric Lemings wrote:
>  
> Could someone give an example of the failures described by this issue?
> In particular, I'm not sure the path should be embedded in the
> executables and the Makefiles should invoke the executables with the
> appropriate runtime library search paths.
>  
> Thanks,
> Brad.
>  
>