From: pierre-marc.fournier@polymtl.ca (Pierre-Marc Fournier)
Subject: [ltt-dev] ltt/ltt-relay-alloc.c:46: error: 'cpu' undeclared
Date: Thu, 02 Oct 2008 12:14:12 -0400 [thread overview]
Message-ID: <48E4F354.9090802@polymtl.ca> (raw)
In-Reply-To: <48E4EC19.2030108@hp.com>
0.27 introduced major and experimental changes. I'm sure Mathieu will
fix this as soon as he reads your post. But if you want to get running
quickly:
- You could go back to 0.26, which was pretty stable and also applies to
2.6.27-rc7, probably -rc8 too.
- Alternatively you could use the LTTng git repository at:
http://git.kernel.org/?p=linux/kernel/git/compudj/linux-2.6-lttng.git;a=summary
You will find the kernel tree with the patches already applied there.
pmf
Alan D. Brunelle wrote:
> I'm attempting to try out LTTng, but ran into this error after the
> following steps:
>
> (1) Git tree w/ Linus' "latest" tree - 2.6.27-rc8 (commit
> 4a7703582836f55a1cbad0e2c1c6ebbee3f9b3a7)
>
> (2) Expanded patch-2.6.27-rc7-lttng-0.27.tar.bz2 into 'patches' directory
>
> (3) Ran 'quilt push -a' which seemed to make a lot of patches...
>
> (4) ran make:
>
> CC ltt/ltt-tracer.o
> ltt/ltt-tracer.c: In function ?ltt_control?:
> ltt/ltt-tracer.c:386: warning: ?trace? may be used uninitialized in this
> function
> ltt/ltt-tracer.c:386: note: ?trace? was declared here
> CC ltt/ltt-relay.o
> CC ltt/ltt-relay-alloc.o
> ltt/ltt-relay-alloc.c: In function ?relay_alloc_buf?:
> ltt/ltt-relay-alloc.c:46: error: ?cpu? undeclared (first use in this
> function)
> ltt/ltt-relay-alloc.c:46: error: (Each undeclared identifier is reported
> only once
> ltt/ltt-relay-alloc.c:46: error: for each function it appears in.)
> make[1]: *** [ltt/ltt-relay-alloc.o] Error 1
> make: *** [ltt] Error 2
>
>
> Looking at the patch patches/lttng-relay-alloc.patch shows that the
> problem is in the patch.
>
> Is this an issue w/ 2.6.27-rc8, and I should go back down to 2.6.27-rc7
> - or is there just a bad patch?
>
> Thanks,
> Alan
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
next prev parent reply other threads:[~2008-10-02 16:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 15:43 Alan D. Brunelle
2008-10-02 16:07 ` Mathieu Desnoyers
2008-10-02 16:14 ` Pierre-Marc Fournier [this message]
2008-10-02 16:18 ` Alan D. Brunelle
2008-10-02 16:23 ` Mathieu Desnoyers
2008-10-02 16:21 ` Alan D. Brunelle
2008-10-02 16:27 ` Mathieu Desnoyers
2008-10-02 16:33 ` Mathieu Desnoyers
2008-10-02 16:40 ` Mathieu Desnoyers
2008-10-02 17:02 ` Alan D. Brunelle
2008-10-02 17:24 ` Mathieu Desnoyers
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=48E4F354.9090802@polymtl.ca \
--to=pierre-marc.fournier@polymtl.ca \
/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