#540: installed versions of dynext/*.so still link to -lparrot in build 
directory
----------------------+-----------------------------------------------------
 Reporter:  doughera  |       Owner:     
     Type:  bug       |      Status:  new
 Priority:  normal    |   Milestone:     
Component:  install   |     Version:     
 Severity:  medium    |    Keywords:     
     Lang:            |       Patch:     
 Platform:            |  
----------------------+-----------------------------------------------------

Comment(by doughera):

 Replying to [comment:1 heidnes]:

 > Briefly summarized: libparrot_ldflags in the config points to the build
 directory.

 I'm not sure if that's really a problem or not, since that variable isn't
 documented anywhere.  However, it looks to me as if it's intended only to
 be used during the build process.  The relevant variable for installed
 versions (also not documented anywhere) appears to be
 inst_libparrot_ldflags.

 > Additionally, on Solaris, RPATH in the installed binaries also point
 into the build
 > directory, while it should point to the installed directory for the
 libraries.

 Actually, what the report says is:
 > In addition under Solaris, the variable "rpath_blib" references the
 build directory as well, similar to libparrot_ldflags

 This is definitely not a problem.  The variable rpath_blib is actually
 documented to be relevant only for the build directory:
 {{{
     # Set -rpath (or equivalent) for executables to find the
     # shared libparrot in the build directory.
 }}}

 So it retains a record of the build directory, but that's not important.
 It is not intended to be used in any way.

 A related problem is that so many of these variables are undocumented, and
 what little documentation there is sprinkled throughout parrot's config/
 directory doesn't get collected or installed anywhere.  So someone working
 with an installed parrot has no easy way to determine whether such
 references are important or harmless.

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/540#comment:2>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets

Reply via email to