#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 | Resolution:
Keywords: | Lang:
Patch: | Platform:
----------------------+-----------------------------------------------------
Comment(by doughera):
Replying to [comment:18 plobsing]:
> Perhaps it is based on a misunderstanding of dynamic linking, but my
preference is a direct and explicit link for all parrot-expecting dynext
libraries. The simple reason is that an implicit "whatever loads me will
have these symbols defined" approach breaks down occasionally.
I understand that as a general idea, but in this specific case, I find it
difficult to imagine a useful program trying to load extra_nci_thunks.so
that hasn't already loaded libparrot.
Moreover, I still don't see any reason for treating some of the
dynext/*.so files differently from the others. Whatever is done for one
should probably be done for all.
If the dynext/*.so files *are* to be linked against -lparrot, then the
appropriate rpath should be set so that the correct version of -lparrot is
found. As a practical matter, this likely means that two copies of each
have to be built: Those built to be used in the build directory need to
be linked with rpath_blib, while those that are to be installed need to be
linked with rpath_lib.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/540#comment:19>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
