Messages in this thread | | | Subject | Re: error in 2.6.37-git10 | From | Eric Dumazet <> | Date | Fri, 14 Jan 2011 12:34:41 +0100 |
| |
Le vendredi 14 janvier 2011 à 12:56 +0200, Felipe Balbi a écrit : > Hi, > > On Fri, Jan 14, 2011 at 11:53:02AM +0100, Piotr Hosowicz wrote: > > >I corrected and am building again. Hope this helps. > > > > I don't know why but it failed again. I disabled and am building again. > > for me it builds ok: > > CC [M] fs/ecryptfs/dentry.o > CC [M] fs/ecryptfs/file.o > CC [M] fs/ecryptfs/inode.o > CC [M] fs/ecryptfs/main.o > CC [M] fs/ecryptfs/super.o > CC [M] fs/ecryptfs/mmap.o > CC [M] fs/ecryptfs/read_write.o > CC [M] fs/ecryptfs/crypto.o > CC [M] fs/ecryptfs/keystore.o > CC [M] fs/ecryptfs/messaging.o > CC [M] fs/ecryptfs/miscdev.o > CC [M] fs/ecryptfs/kthread.o > CC [M] fs/ecryptfs/debug.o > LD [M] fs/ecryptfs/ecryptfs.o > > weird. >
This is because it was fixed meanwhile
commit 6254b32b5791e47ba1c679d023f26985fa34755a Author: Linus Torvalds <torvalds@linux-foundation.org> Date: Thu Jan 13 17:19:38 2011 -0800
ecryptfs: fix broken build
Stephen Rothwell reports that the vfs merge broke the build of ecryptfs. The breakage comes from commit 66cb76666d69 ("sanitize ecryptfs ->mount()") which was obviously not even build tested. Tssk, tssk, Al. This is the minimal build fixup for the situation, although I don't have a filesystem to actually test it with. Reported-by: Stephen Rothwell <sfr@canb.auug.org.au> Cc: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |