#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 heidnes):
Replying to [comment:1 doughera]:
> Replying to [ticket:762 ingmar]:
> > If parrot is installed to a staging area (ie DESTDIR=/foo passed to
the make install call), then parrot_config --dump contains references to
the build directory:
>
> Actually, it contains references to the build directory whether or not
you use DESTDIR.
>
> 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). Why should then the
installed parrot config contain any references whatsoever to the build
directory, which will
in this scenario not exist?
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/762#comment:2>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
