On 05/09/2013 04:54 AM, Peter Zijlstra wrote: > On Thu, May 09, 2013 at 12:19:07AM -0400, Sasha Levin wrote: >> liblockdep is a tiny wrapper built around kernel/lockdep.c. The aim is to >> provide the same functionality the kernel gets from lockdep to userspace. >> >> The bulk of the code here is the LD_PRELOAD support which provides users >> an easy way to test their code without having to integrate liblockdep into >> said code. Simply doing: >> >> lockdep my_app >> >> Would provide lockdep support to my_app. >> >> There is also a small test suite to test both mutexes and rwlocks, it's >> based on the tests in lib/locking-selftest.c. >> >> This entire patch series was reviewed by lockdep maintainers and >> accepted to >> the tip tree previously. It was pulled out so that the potential merge >> of >> liblockdep won't delay the rest of the commits in the tip locking tree. >> >> For some more background about this entire thing, the folks at LWN did >> an awesome overview: http://lwn.net/Articles/536363/ >> >> >> Changes from v1: >> - Addressed Peter's comments. >> > > root@twins:/usr/src/linux-2.6/tools/lib/lockdep# make > CC FPIC common.o > In file included from ./uinclude/linux/lockdep.h:13:0, > from /usr/src/linux-2.6/tools/lib/lockdep/common.c:4: > ./../../../include/linux/lockdep.h:21:27: fatal error: linux/linkage.h: No > such file or directory > compilation terminated. > make: *** [common.o] Error 1
Oh, Ingo had a similar problem - you're using Quilt and that mishandles the creation of empty files. You'll need to poke it stronger :) I did notice a different issue due to a recent commit to kernel/lockdep.c, I'll resend it again. Thanks, Sasha -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
