linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Mathieu Desnoyers <compudj@krystal.dyndns.org>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Ext4 Developers List <linux-ext4@vger.kernel.org>,
	ltt-dev@lists.casi.polymtl.ca, linux-kernel@vger.kernel.org
Subject: Re: [ltt-dev] LTTng 0.74 for Linux 2.6.28 (ext4 tracepoints) (fixed in LTTng 0.78)
Date: Tue, 13 Jan 2009 19:13:46 -0500	[thread overview]
Message-ID: <20090114001346.GB14730@mit.edu> (raw)
In-Reply-To: <20090113225827.GA5791@Krystal>

On Tue, Jan 13, 2009 at 05:58:27PM -0500, Mathieu Desnoyers wrote:
> > 
> > -ECANTBUILD
> > 
> Thanks for the report. This should be fixed in LTTng 0.78 now.

Out of curiosity, do you maintain a branch of LTTNG versus any of the
-rc kernels, or do you only track the stable kernels?  I tried pulling
LTTNG 0.78 against the most recent Linus mainline and got a whole pile
of conflicts.

I then tried building LTTng 0.78 and got build failures:

  CC      arch/x86/kernel/init_task.o
distcc[27501] ERROR: compile /var/cache/ccache/init_task.tmp.closure.27497.i on localhost failed
/usr/projects/linux/ext4/arch/x86/kernel/init_task.c:35: error: unknown field ‘user_markers_mutex’ specified in initializer
/usr/projects/linux/ext4/arch/x86/kernel/init_task.c:35: warning: braces around scalar initializer
/usr/projects/linux/ext4/arch/x86/kernel/init_task.c:35: warning: (near initialization for ‘init_task.latency_record_count’)
/usr/projects/linux/ext4/arch/x86/kernel/init_task.c:35: error: field name not in record or union initializer
/usr/projects/linux/ext4/arch/x86/kernel/init_task.c:35: error: (near initialization for ‘init_task.latency_record_count’)

Looks like CONFIG_MARKERS_USERSPAC is busted....

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-01-14  0:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090109235449.GA21999@Krystal>
2009-01-10 16:11 ` [ltt-dev] LTTng 0.74 for Linux 2.6.28 (ext4 tracepoints) Mathieu Desnoyers
2009-01-13 22:33   ` KOSAKI Motohiro
2009-01-13 22:58     ` [ltt-dev] LTTng 0.74 for Linux 2.6.28 (ext4 tracepoints) (fixed in LTTng 0.78) Mathieu Desnoyers
2009-01-13 23:57       ` KOSAKI Motohiro
2009-01-14  5:20         ` Mathieu Desnoyers
2009-01-14  0:13       ` Theodore Tso [this message]
2009-01-15  1:45         ` Mathieu Desnoyers
2009-01-15  3:20           ` 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=20090114001346.GB14730@mit.edu \
    --to=tytso@mit.edu \
    --cc=compudj@krystal.dyndns.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@lists.casi.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;
as well as URLs for NNTP newsgroup(s).