This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/20264] New: Load tapsets from $libdir for multiarch
- From: "bugzilla at tecnocode dot co.uk" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Thu, 16 Jun 2016 17:16:00 +0000
- Subject: [Bug tapsets/20264] New: Load tapsets from $libdir for multiarch
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=20264
Bug ID: 20264
Summary: Load tapsets from $libdir for multiarch
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tapsets
Assignee: systemtap at sourceware dot org
Reporter: bugzilla at tecnocode dot co.uk
Target Milestone: ---
Tapsets for libraries have the path of the library hard-coded in them, and are
installed in /usr/share at the moment. Architecture-specific hard-coded paths
should not be in /usr/share.
In order to support multiarch, SystemTap should support loading tapsets from
multiarch directories beneath /usr/lib; e.g.
/usr/lib/arm-linux-gnueabihf/systemtap/tapset.
https://wiki.debian.org/Multiarch/Implementation#What_does_the_end_result_look_like.3F
Bug #20203 is about searching the library path for process("mylib.so"); I think
for multiarch we need to keep the full paths in the process() call; but allow
installation of multiple .stp files (one per architecture per library).
--
You are receiving this mail because:
You are the assignee for the bug.