From: Mark Wielaard <mjw@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: [PATCH] Allow to disable components
Date: Thu, 13 Oct 2016 12:04:42 +0200 [thread overview]
Message-ID: <1476353082.21750.185.camel@redhat.com> (raw)
In-Reply-To: 1476352283.21750.183.camel@redhat.com
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
On Thu, 2016-10-13 at 11:51 +0200, Mark Wielaard wrote:
> We this split up and why do you want to enable/disable these specific
> parts?
>
> I don't think it makes sense to be able to not build the ebl backends
> (unless you don't build libasm, libdw and also not the tools - only
> libelf doesn't directly use the backends). And obviously various tools
> won't build if you disable either libdw or libasm. And libasm won't
> build without libdw.
>
> arpg is part of the libdwfl interface, so isn't really specific to the
> tools.
And again, the testsuite needs to be adapted to skip any tests that
don't make sense when some parts are disabled.
Thanks,
Mark
next reply other threads:[~2016-10-13 10:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 10:04 Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-14 1:56 Akihiko Odaki
2016-10-13 9:51 Mark Wielaard
2016-10-11 14:11 Akihiko Odaki
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=1476353082.21750.185.camel@redhat.com \
--to=mjw@redhat.com \
--cc=elfutils-devel@lists.fedorahosted.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).