From: Laurent Stacul <laurent.stacul@gmail.com>
To: elfutils-devel@sourceware.org
Subject: Re: On demand static/shared libs and binary linkage
Date: Thu, 07 Jun 2018 13:59:00 -0000 [thread overview]
Message-ID: <CAGdu8SLR-XecUcmzLCF02qKbrt0rYsLCSRr0MRfC-0sRb1-t+w@mail.gmail.com> (raw)
In-Reply-To: <70f9f01b-fa1e-36a8-9837-d265c3fa6ef2@qt.io>
Understood.
In this case, there are 2 solutions:
- we completely remove the call to dlopen
- we keep the call to dlopen from the shared lib version of libdw and
embed all the backends code in the archive
I don't know if the second solution is worth the additional
work/complexity. What do you think ?
Laurent
next prev parent reply other threads:[~2018-06-07 13:59 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
2018-06-07 13:59 ` Laurent Stacul [this message]
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=CAGdu8SLR-XecUcmzLCF02qKbrt0rYsLCSRr0MRfC-0sRb1-t+w@mail.gmail.com \
--to=laurent.stacul@gmail.com \
--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).