From: Ulf Hermann <ulf.hermann@qt.io>
To: elfutils-devel@sourceware.org
Subject: Re: On demand static/shared libs and binary linkage
Date: Thu, 07 Jun 2018 08:09:00 -0000 [thread overview]
Message-ID: <70f9f01b-fa1e-36a8-9837-d265c3fa6ef2@qt.io> (raw)
In-Reply-To: <CAGdu8SJgqoPTvVC-0U9dyrfp+hGV=Svv1A217Xo0eyCB4sk29w@mail.gmail.com>
Hi,
> - the delivered libs cannot be 100% static archives. Depending on the
> machine the libelf is used, some backend code are dlopen'd. So at
> least, the backends code must be delivered as shared lib (in the by
> default EBL directory)
The backends are for libdw, not libelf, and they are not about the
machine you are _running_ this on, but about the machine the binaries
you are looking at were compiled for. The dlopen is not technically
necessary. We could just compile all the backends into libdw. The
backend interface is private API and therefore you shouldn't use
"external" backends anyway. The downside would be that libdw gets
bigger, but the upside of not having to deal with dlopen and rpath would
be easily worth it, at least for my use case.
This has been on my wish list for a while, but I haven't gotten around
to do it, yet.
Ulf
next prev parent reply other threads:[~2018-06-07 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 8:01 Laurent Stacul
2018-06-07 8:09 ` Ulf Hermann [this message]
2018-06-07 13:59 ` Laurent Stacul
2018-06-07 22:01 ` Mark Wielaard
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=70f9f01b-fa1e-36a8-9837-d265c3fa6ef2@qt.io \
--to=ulf.hermann@qt.io \
--cc=elfutils-devel@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).