From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] LTTng 0.85 for kernel 2.6.28
Date: Thu, 20 May 2010 09:55:58 -0400 [thread overview]
Message-ID: <20100520135558.GA9108@Krystal> (raw)
In-Reply-To: <34F012EAAD78FB49A2AFF01BF6DCE07602A4AA5D@ASHWA.Asiapac.Arm.com>
You might want to move to a newer LTTng version, or try removing the
psrwlock* patches from the patchset.
Thanks,
Mathieu
* Jyotiswarup Raiturkar (Jyotiswarup.Raiturkar at arm.com) wrote:
> I'm trying to install patch-2.6.28-lttng-0.85.tar on 2.6.28, but I'm
> getting compilation errors. Is there a header file <linux/spinlock.h>
> missing or something wrong with my setup/
>
> In file included from lib/psrwlock.c:13:
> include/linux/psrwlock.h: In function 'write_context_disable':
> include/linux/psrwlock.h:187: error: implicit declaration of function
> 'local_bh_disable'
> include/linux/psrwlock.h: In function 'write_context_enable':
> include/linux/psrwlock.h:197: error: implicit declaration of function
> 'local_bh_enable'
> In file included from include/linux/spinlock.h:56,
> from include/linux/seqlock.h:29,
> from include/linux/time.h:8,
> from include/linux/timex.h:57,
> from include/linux/sched.h:54,
> from include/linux/freezer.h:6,
> from lib/psrwlock.c:16:
> include/linux/bottom_half.h: At top level:
> include/linux/bottom_half.h:4: warning: conflicting types for
> 'local_bh_disable'
> include/linux/psrwlock.h:187: warning: previous implicit declaration of
> 'local_bh_disable' was here
> include/linux/bottom_half.h:7: warning: conflicting types for
> 'local_bh_enable'
> include/linux/psrwlock.h:197: warning: previous implicit declaration of
> 'local_bh_enable' was here
> lib/psrwlock.c: In function '__psread_lock_slow':
> lib/psrwlock.c:368: warning: unused variable 'subclass'
> lib/psrwlock.c: In function '__pswrite_lock_slow_common':
> lib/psrwlock.c:689: warning: unused variable 'subclass'
> lib/psrwlock.c:683: warning: unused variable 'task'
> lib/psrwlock.c: In function '_pswrite_unlock_slow':
> lib/psrwlock.c:860: warning: unused variable 'nested'
> make[1]: *** [lib/psrwlock.o] Error 1
> make: *** [lib] Error 2
>
> Thanks
> Jyotiswarup Raiturkar
> --
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
prev parent reply other threads:[~2010-05-20 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 19:17 [ltt-dev] [RELEASE] LTTng 0.215 for kernel 2.6.33.4 Mathieu Desnoyers
2010-05-20 11:27 ` [ltt-dev] LTTng 0.85 for kernel 2.6.28 Jyotiswarup Raiturkar
2010-05-20 13:55 ` Mathieu Desnoyers [this message]
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=20100520135558.GA9108@Krystal \
--to=compudj@krystal.dyndns.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