From: jbernard@debian.org (Jon Bernard)
Subject: [ltt-dev] Debian libust-dev package
Date: Mon, 7 Feb 2011 23:01:30 -0500 [thread overview]
Message-ID: <20110208040128.GA5580@starquasia> (raw)
In-Reply-To: <AANLkTikbZQOxr8-T9fE8ynr=t6NLRz-8inAn2pz-Z2ht@mail.gmail.com>
* Stefan Hajnoczi <stefanha at gmail.com> wrote:
> Hi Jon,
> I am trying to build QEMU from source with UST tracing on Debian
> testing. I've used your libust-dev package successfully in the past
> but am hitting issues this time.
>
> It seems the libust-dev 0.5-1+squeeze1 does not depend on liburcu-dev
> 0.5.2-1. The urcu header files are included by the ust header files
> so this is needed.
Yes, so this is technically a bug in the Debian package. I did not
catch the package dependency in time for the release freeze. I was
hoping no one would notice ;)
> With libust-dev and liburcu-dev installed I cannot compile the
> following program (which used to work fine):
> #include <ust/tracepoint.h>
> #include <ust/marker.h>
> int main(void) { return 0; }
As squeeze was just released this past weekend, packages from unstable
have started migrating into the new testing (which will eventually
become wheezy) and I believe this version mismatch is a result of
a partial migration. In other words, liburcu has been updated, but ust
has not yet. If I am correct, a newer version of ust (from unstable)
should show up in testing quite soon. Would you mind listing the package
versions of the relevant pieces (ust and urcu) and also the contents of
/etc/apt/sources.list?
--
Jon
next prev parent reply other threads:[~2011-02-08 4:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 16:59 Stefan Hajnoczi
2011-02-07 17:13 ` Yannick Brosseau
2011-02-07 17:14 ` Mathieu Desnoyers
2011-02-08 4:01 ` Jon Bernard [this message]
2011-02-08 9:59 ` Stefan Hajnoczi
2011-02-09 0:19 ` Jon Bernard
2011-02-09 7:49 ` Stefan Hajnoczi
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=20110208040128.GA5580@starquasia \
--to=jbernard@debian.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