From: Christoph Hellwig <hch@infradead.org>
To: Carlo Wood <carlo@alinoe.com>,
ext3grep@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [ext3grep] compile error
Date: Fri, 14 Mar 2008 14:14:55 -0400 [thread overview]
Message-ID: <20080314181455.GA15351@infradead.org> (raw)
In-Reply-To: <20080314170004.GA25174@alinoe.com>
On Fri, Mar 14, 2008 at 06:00:04PM +0100, Carlo Wood wrote:
> This seem a bug in linux/ext3_fs.h. I was able to reproduce this on
> debian sid, meaning kernel (headers) 2.6.24.
No, the problem is that the tool you're compiling is using kernel
headers which it shouldn't use at all. Please use the headers from
e2fslibs-dev in /usr/include/esxt2fs/ instead. And yes, they provide
ext3 defintions despite the ext2 name.
The only kernel todo here is to remove ext3*.h from the list of exported
headers ASAP.
next prev parent reply other threads:[~2008-03-14 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1f45affd0803140826m34d9eee5veb8069e215d55fcf@mail.gmail.com>
2008-03-14 17:00 ` [ext3grep] compile error Carlo Wood
2008-03-14 18:14 ` Christoph Hellwig [this message]
2008-03-14 20:55 ` Theodore Tso
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=20080314181455.GA15351@infradead.org \
--to=hch@infradead.org \
--cc=carlo@alinoe.com \
--cc=ext3grep@googlegroups.com \
--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