linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: nicholas.dokos@hp.com, linux-ext4@vger.kernel.org
Subject: Compile error in pu branch of e2fsprogs.
Date: Thu, 20 Aug 2009 12:04:58 -0400	[thread overview]
Message-ID: <8693.1250784298@alphaville.usa.hp.com> (raw)

Hi Ted,

I got this error when trying to build the pu branch of e2fsprogs:

,----
|         ...
| 	CC ../../misc/e4defrag.c
| ../../misc/e4defrag.c:326:2: warning: #warning Using locally defined fallocate syscall interface.
| ../../misc/e4defrag.c: In function ‘file_frag_count’:
| ../../misc/e4defrag.c:627: error: ‘FS_IOC_FIEMAP’ undeclared (first use in this function)
| ../../misc/e4defrag.c:627: error: (Each undeclared identifier is reported only once
| ../../misc/e4defrag.c:627: error: for each function it appears in.)
| ../../misc/e4defrag.c: In function ‘get_file_extents’:
| ../../misc/e4defrag.c:940: error: ‘FS_IOC_FIEMAP’ undeclared (first use in this function)
| make[2]: *** [e4defrag.o] Error 1
| make[2]: Leaving directory `/home/nick/src/e2fsprogs/build/misc'
| make[1]: *** [all-progs-recursive] Error 1
| make[1]: Leaving directory `/home/nick/src/e2fsprogs/build'
| make: *** [all] Error 2
| nick@shifter:~/src/e2fsprogs/build$ uname -r
| 2.6.31-rc6
`----

Currently, the #define is in filefrag.c:

,----
| nick@shifter:~/src/e2fsprogs$ find . -type f | xargs grep FS_IOC
| ./misc/filefrag.c:#define FS_IOC_FIEMAP	_IOWR('f', 11, struct fiemap)
| ./misc/filefrag.c:		rc = ioctl(fd, FS_IOC_FIEMAP, (unsigned long) fiemap);
| ./misc/e4defrag.c:/* The following macro is used for ioctl FS_IOC_FIEMAP
| ./misc/e4defrag.c:	ret = ioctl(fd, FS_IOC_FIEMAP, &fiemap_buf);
| ./misc/e4defrag.c:		ret = ioctl(fd, FS_IOC_FIEMAP, fiemap_buf);
| ./lib/ext2fs/fiemap.h: * FS_IOC_FIEMAP ioctl infrastructure.
`----

I moved it from there to lib/ext2fs/fiemap.h and that fixes it.

Thanks,
Nick
--
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

             reply	other threads:[~2009-08-20 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-20 16:04 Nick Dokos [this message]
2009-08-20 16:13 ` Compile error in pu branch of e2fsprogs Eric Sandeen
2009-08-20 16:32   ` Nick Dokos
2009-08-20 16:41     ` Eric Sandeen
2009-08-23 14:48       ` 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=8693.1250784298@alphaville.usa.hp.com \
    --to=nicholas.dokos@hp.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).