From: "Maciej W. Rozycki" <macro@embecosm.com>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: Vladimir Mezentsev via Binutils <binutils@sourceware.org>
Subject: Re: [PATCH V4] gprofng: a new GNU profiler
Date: Wed, 2 Feb 2022 12:40:58 +0000 (GMT) [thread overview]
Message-ID: <alpine.DEB.2.20.2202021233200.11348@tpp.orcam.me.uk> (raw)
In-Reply-To: <87fsp9jli4.fsf@oracle.com>
On Thu, 27 Jan 2022, Jose E. Marchesi via Binutils wrote:
> > It looks like you configured build without --enable-shared.
> > If yes, this is expected.
>
> Woudn't it be better to skip building gprofng in case no --enable-shared
> is specified at `configure' time?
Is it actually necessary to require `--enable-shared' in the first place
for the program to work?
The thing is there is (otherwise) little point in using the option with
binutils, given that both libbfd and libopcodes are internal libraries not
for general use and neither provides a stable ABI, so every revision would
have to be separately installed if any external programs were to use them.
Therefore having these libraries built as DSOs causes all the drawbacks
of dynamic loading while no advantages of same are virtually used, and
consequently I believe hardly anyone uses such a configuration.
Maciej
next prev parent reply other threads:[~2022-02-02 12:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fcc77804-0d0c-0f8e-5c3b-3ac034340b1a@oracle.com>
2021-11-03 18:05 ` Vladimir Mezentsev
2021-11-15 18:13 ` Ping: " Vladimir Mezentsev
2021-11-29 17:34 ` Vladimir Mezentsev
2021-12-10 9:38 ` Nick Clifton
2021-12-10 17:31 ` Vladimir Mezentsev
2021-12-13 15:13 ` Nick Clifton
2021-12-16 22:22 ` Vladimir Mezentsev
2022-01-12 0:48 ` Vladimir Mezentsev
2022-01-12 12:42 ` Nick Clifton
2022-01-12 15:17 ` Jose E. Marchesi
2022-01-12 15:23 ` Jose E. Marchesi
[not found] ` <c26c71b2-8cf1-2eef-206f-14c4774b2ba0@oracle.com>
2022-01-26 12:04 ` Nick Clifton
2022-01-26 17:10 ` Vladimir Mezentsev
2022-01-27 14:34 ` Jose E. Marchesi
2022-02-02 12:40 ` Maciej W. Rozycki [this message]
2022-02-02 16:30 ` Jose E. Marchesi
2022-02-03 6:23 ` Vladimir Mezentsev
2022-02-03 11:02 ` Maciej W. Rozycki
2022-02-03 12:16 ` Jose E. Marchesi
2022-03-02 19:47 ` Vladimir Mezentsev
2022-03-04 13:53 ` Nick Clifton
2022-03-07 21:42 ` Vladimir Mezentsev
2022-03-07 21:57 ` H.J. Lu
2022-03-07 22:25 ` Vladimir Mezentsev
2022-03-09 16:36 ` Nick Clifton
2022-03-09 21:13 ` Vladimir Mezentsev
2022-03-14 11:12 ` Martin Liška
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=alpine.DEB.2.20.2202021233200.11348@tpp.orcam.me.uk \
--to=macro@embecosm.com \
--cc=binutils@sourceware.org \
--cc=jose.marchesi@oracle.com \
/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).