#207: Unsecure RUNPATHS in parrot 0.90
---------------------+------------------------------------------------------
Reporter: lu_zero | Owner: jkeenan
Type: bug | Status: assigned
Priority: normal | Milestone:
Component: install | Version: 0.9.0
Severity: low | Keywords:
Lang: | Patch:
Platform: |
---------------------+------------------------------------------------------
Changes (by jkeenan):
* owner: => jkeenan
* status: new => assigned
Comment:
Replying to [comment:5 doughera]:
items listed in the OP; or (b) identify which items have been resolved?
>
> On Linux, you can use chrpath -l to check. I think they are all ok now,
and you can close the ticket.
Never having used `chrpath` before, I had to install its Debian package to
do this. I checked on all the executables and all the `.so` files. In
the case of the executables, the output always looked like this:
{{{
$ chrpath -l parrot
parrot: RPATH=/home/jimk/gitwork/parrot/blib/lib
}}}
In the case of the `.so` files, the output always looked like this:
{{{
$ chrpath -l ./blib/lib/libparrot.so.3.0.0
./blib/lib/libparrot.so.3.0.0: no rpath or runpath tag found.
$ $ chrpath -l runtime/parrot/dynext/bit_ops.so
runtime/parrot/dynext/bit_ops.so: no rpath or runpath tag found.
}}}
Is that the expected output? Does it suffice to close the ticket?
Thank you very much.
kid51
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/207#comment:6>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
