#762: parrot_config --dump: libparrot_linkflags, rpath_blib contain references
to
the build directory if parrot is installed to a DESTDIR first
--------------------+-------------------------------------------------------
Reporter: ingmar | Type: bug
Status: new | Priority: normal
Milestone: | Component: configure
Version: 1.2.0 | Severity: medium
Keywords: | Lang:
Patch: | Platform: linux
--------------------+-------------------------------------------------------
Comment(by doughera):
Replying to [comment:2 heidnes]:
> Replying to [comment:1 doughera]:
> > Replying to [ticket:762 ingmar]:
> > However, it's not at all clear to me why this is a problem. Those
variables are currently intended to only be used in the build directory.
See the first few replies to TT #540 for more details.
>
> Hm, my take on this is slightly different.
>
> Surely, it must be a goal to make it possible to share one installed
parrot between multiple
> higher-level languages, using a binary package of the shared parrot (I
know, e.g. rakudo isn't
> able to use a shared parrot ... yet).
>
Yes, but this is irrelevant, since those variables you reference are not
currently intended to be used by an installed parrot,
> Why should then the
> installed parrot config contain any references whatsoever to the build
directory, which will
> in this scenario not exist?
It's not that it "should" contain such references. The question is why
would anyone care if it contains such references. They are not intended
to be used. They are useless. Irrelevant.
Whether parrot_config should be changed to make them useful and relevant
is the subject of TT #649.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/762#comment:3>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
