#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 plobsing):
Replying to [comment:15 jkeenan]:
> plobsing,
>
> Could you comment on the issues raised in comments 10+ in this ticket?
Can we eliminate the linkage of extra_nci_thunks against libparrot?
extra_nci_thunks.c includes function calls to
Parrot_pcc_fill_params_from_c_args(), which is part of libparrot. These
calls are essential to the operation of this library, therefore it must be
linked against libparrot to operate correctly.
As to the purpose of this library, it is the repetition of
extra_thunks.nci as a dynlib, used to demonstrate the viability of using
dynlibs to provide additional nci thunks. One can configure --without-
extra-nci-thunks, load this library, and run tests that depend on these
thunks (eg: t/pmc/nci.t) which would normally fail with this
configuration. I intended the configure-without-extra/load-as-separate-
library as the default approach, however, this approach never caught on
(I've heard complaints that "you can't use anything but the built-in
signatures" months after this was no longer the case). I think it still
has value, although I'm a bit burned out on the whole NCI thing.
> Thank you very much.
>
> kid51
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/540#comment:16>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
