#207: Unsecure RUNPATHS in parrot 0.90
---------------------+------------------------------------------------------
Reporter: lu_zero | Owner: jkeenan
Type: bug | Status: closed
Priority: normal | Milestone:
Component: install | Version: 0.9.0
Severity: low | Resolution: fixed
Keywords: | Lang:
Patch: | Platform:
---------------------+------------------------------------------------------
Changes (by doughera):
* status: assigned => closed
* resolution: => fixed
Comment:
Replying to [comment:6 jkeenan]:
> 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?
To be absolutely thoroughly paranoid, you would have to run 'make install'
and run that command on the installed versions, not on the versions in the
build directory. However, parrot doesn't actually build 'installable'
versions of dynext/*.so anyway, so it wouldn't matter.
I've closed the ticket.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/207#comment:7>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
