From: Li Zefan <lizf@cn.fujitsu.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-btrfs@vger.kernel.org, Chris Mason <chris.mason@oracle.com>
Subject: Re: btrfs build failure in latest git
Date: Wed, 12 Jan 2011 11:00:06 +0800 [thread overview]
Message-ID: <4D2D1936.2070201@cn.fujitsu.com> (raw)
In-Reply-To: <4D2CE678.10607@garzik.org>
Jeff Garzik wrote:
>=20
> Tree as of commit 7bc4a4ce68f8c6d064ea949446852e996526f692 dies durin=
g btrfs build on x86-64:
>=20
> CC [M] fs/btrfs/ctree.o
> In file included from fs/btrfs/ctree.c:21:0:
> fs/btrfs/ctree.h:1003:17: error: field =91super_kobj=92 has incomplet=
e type
> fs/btrfs/ctree.h:1074:17: error: field =91root_kobj=92 has incomplete=
type
> make[2]: *** [fs/btrfs/ctree.o] Error 1
> make[1]: *** [fs/btrfs] Error 2
> make: *** [fs] Error 2
>=20
Should be caused by this commit:
commit 57cc7215b70856dc6bae8e55b00ecd7b1d7429b1
Author: Alexey Dobriyan <adobriyan@gmail.com>
Date: Mon Jan 10 08:18:25 2011 +0200
headers: kobject.h redux
=20
Remove kobject.h from files which don't need it, notably,
sched.h and fs.h.
So the fix is to include kobject.h explicitly in ctree.h.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-01-12 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 23:23 btrfs build failure in latest git Jeff Garzik
2011-01-12 3:00 ` Li Zefan [this message]
2011-01-12 9:30 ` [PATCH] fs/btrfs: Fix build of ctree Stefan Schmidt
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=4D2D1936.2070201@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=chris.mason@oracle.com \
--cc=jeff@garzik.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).