From: yannick.brosseau@gmail.com (Brosseau, Yannick)
Subject: [ltt-dev] lttng-ust can't build on ppc?
Date: Thu, 10 Feb 2011 00:59:20 -0500 [thread overview]
Message-ID: <AANLkTikaxfDomp4NPFJ3HX3QaXEVAE9Ytros7K-rTPuN@mail.gmail.com> (raw)
Message-ID: <20110210055920.JnFPyl0PLMMz0-sV34zV75iE1UzjKMTjsNmq5AWC2UQ@z> (raw)
In-Reply-To: <1865303E0DED764181A9D882DEF65FB68621EAFDBF@shsmsx502.ccr.corp.intel.com>
Please see the patch I've posted earlier today. It fix this.
Le 2011-02-10 00:55, "Cui, Dexuan" <dexuan.cui at intel.com> a ?crit :
> Hi, I got the following build failure on ppc:
>
> | make[2]: Entering directory 'ust-0.11/libust'
> | CC libust_la-buffers.lo
> | In file included from buffers.c:30:0:
> | ../include/ust/clock.h: In function 'trace_clock_frequency':
> | ../include/ust/clock.h:111:6: error: 'CLOCK_TRACE' undeclared (first use
in this function)
> | ../include/ust/clock.h:111:6: note: each undeclared identifier is
reported only once for each function it appears in
> | ../include/ust/clock.h:112:17: error: 'CLOCK_TRACE_FREQ' undeclared
(first use in this function)
> | ../include/ust/clock.h:113:13: error: dereferencing pointer to
incomplete type
> | make[2]: *** [libust_la-buffers.lo] Error 1
> | make[2]: Leaving directory `ust-0.11/libust'
>
> I think commit 9c6bb08180ab0a65bbf3d47247a9d36e257fa44a introduced this
issue.
>
> Can someboby please have a look?
>
> Thanks,
> -- Dexuan
>
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/ltt-dev/attachments/20110210/b08fe17d/attachment.htm>
next prev parent reply other threads:[~2011-02-10 5:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 5:54 Cui, Dexuan
2011-02-10 5:59 ` Brosseau, Yannick [this message]
2011-02-10 5:59 ` Brosseau, Yannick
2011-02-10 5:59 ` Brosseau, Yannick
2011-02-10 6:30 ` Cui, Dexuan
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=AANLkTikaxfDomp4NPFJ3HX3QaXEVAE9Ytros7K-rTPuN@mail.gmail.com \
--to=yannick.brosseau@gmail.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