From: "bugzilla at tecnocode dot co.uk" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/20264] New: Load tapsets from $libdir for multiarch
Date: Thu, 16 Jun 2016 17:16:00 -0000 [thread overview]
Message-ID: <bug-20264-6586@http.sourceware.org/bugzilla/> (raw)
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.
next reply other threads:[~2016-06-16 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 17:16 bugzilla at tecnocode dot co.uk [this message]
2016-06-16 17:35 ` [Bug tapsets/20264] " fche at redhat dot com
2016-06-16 20:14 ` bugzilla at tecnocode dot co.uk
2016-06-16 20:15 ` bugzilla at tecnocode dot co.uk
2016-06-16 20:23 ` fche at redhat dot com
2016-06-16 20:24 ` fche at redhat dot com
2016-06-16 20:49 ` bugzilla at tecnocode dot co.uk
2016-06-16 21:04 ` fche at redhat dot com
2019-05-21 17:43 ` fche at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-20264-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).