From: Andrew Shewmaker <agshew@gmail.com>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Ιnstrumenting RADOS with Zipkin + LTTng
Date: Fri, 7 Nov 2014 10:29:05 -0700 [thread overview]
Message-ID: <20141107172905.GA7184@localhost> (raw)
In-Reply-To: <alpine.DEB.2.00.1411070230091.15135@cobra.newdream.net>
On Fri, Nov 07, 2014 at 02:32:51AM -0800, Sage Weil wrote:
>
> On Thu, 30 Oct 2014, Andrew Shewmaker wrote:
> >
> > Should I put effort into adding a "--with-blkin" or "--with-zipkin"
> > option to autoconf?
>
> Is it statically or dynamically linked?
>
> Probably a first step is to get it in the gitbuilder (test/qa) builds.
Okay, I'll work on getting it in gitbuilder.
It's dynamically linked, and I imagine blkin will be useful outside
of Ceph, at least for apps built on top of Ceph.
So before getting it in gitbuilder, I'm thinking I'll add blkin as a
submodule that is always built. Then after it's in gitbuilder I'll put
in autoconf support and build libblkin and libblkin-dev packages?
Would you prefer autoconf to enable blkin by default?
Andrew
next prev parent reply other threads:[~2014-11-07 17:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 18:49 Ιnstrumenting RADOS with Zipkin + LTTng Andrew Shewmaker
2014-11-07 10:32 ` Sage Weil
2014-11-07 17:29 ` Andrew Shewmaker [this message]
2014-11-07 14:18 ` Mark Nelson
2014-11-07 14:36 ` Matt W. Benjamin
-- strict thread matches above, loose matches on Subject: below --
2014-08-01 16:28 Marios-Evaggelos Kogias
2014-08-01 20:17 ` Samuel Just
2014-08-01 20:24 ` Samuel Just
[not found] ` <CAFu9Dv1Aqsf69=fXGZ1QjgQuvmXyaDGX0vk91MAT=6QuWznXDw@mail.gmail.com>
2014-08-05 16:22 ` Marios-Evaggelos Kogias
2014-08-13 21:21 ` Samuel Just
2014-08-01 20:54 ` Adam Crume
2014-08-05 16:18 ` Marios-Evaggelos Kogias
2014-08-01 16:14 Marios-Evaggelos Kogias
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=20141107172905.GA7184@localhost \
--to=agshew@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
/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