[svn:parrot] r38364 - trunk/tools/dev

Andy Dougherty doughera at lafayette.edu
Wed Apr 29 13:28:56 UTC 2009


On Wed, 29 Apr 2009, Michael Schroeder wrote:

> On Wed, Apr 29, 2009 at 08:34:21AM -0400, Andy Dougherty wrote:
> > I haven't tried to use either, but I also can't imagine how you could 
> > really test or develop either until TT #495 "[TODO] remove hardcoded path 
> > from installable pbc_to_exe"
> 
> To fix this, MANIFEST.generated needs to include
> src/install_config.o, src/null_config.o, and src/parrot_config.o.
> 
> The question is just where to put those three files.

No, that won't help.  installable_pbc_to_exe is already linked with 
src/install_config.o as part of the build process.  Copying 
src/install_config.o to the installation directory won't actually do 
anything right now, since pbc_to_exe won't go looking for it anyway.

The problem is that install_config.c is wrong.

> > and TT #540 "installed versions of 
> > dynext/*.so still link to -lparrot in build directory" are fixed.
> 
> Add "--disable-rpath" to your Configure.pl call.

Yes, I realize that will work around the problem.  But it shouldn't be 
necessary, and creates two new problems:  During the build process, 
LD_LIBRARY_PATH (or equivalent) will need to be manually set.  Then, after 
install, LD_LIBRARY_PATH (or equivalent) will need to be set to include 
the installed parrot library directory for every process that invokes 
parrot.

-- 
    Andy Dougherty		doughera at lafayette.edu


More information about the parrot-dev mailing list