Ed W wrote: > [email protected] wrote: > >> Ed W: >> >> >>> I think you can repro my setup using >>> http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.26.5.tar.bz2 >>> patched with: >>> http://vserver.13thfloor.at/Experimental/patch-2.6.29.5-vs2.3.0.36.14.diff >>> and of course: >>> aufs-standalone.patch from git commit above (branch aufs2-29) >>> >>> >> Tried and succeeded. >> See below in detail. >> >> > > > Hmm, now everything is fine for me also... This is very curious >
There is something funny going on with the KDIR variable # KDIR=/usr/src/linux-2.6.29.5-vs2.3.0.36.14 make -I/usr/src/test/aufs2-standalone/include -DCONFIG_AUFS_MODULE -UCONFIG_AUFS -DCONFIG_AUFS_BRANCH_MAX_127 -DCONFIG_AUFS_HINOTIFY -DCONFIG_AUFS_DEBUG make -C /lib/modules/2.6.29.5-vs2.3.0.36.14/build M=/usr/src/test/aufs2-standalone/fs/aufs EXTRA_CFLAGS="-I/usr/src/test/aufs2-standalone/include -DCONFIG_AUFS_MODULE -UCONFIG_AUFS -DCONFIG_AUFS_BRANCH_MAX_127 -DCONFIG_AUFS_HINOTIFY -DCONFIG_AUFS_DEBUG" modules make[1]: Entering directory `/usr/src/test/linux-2.6.29.5' ..snip... make[1]: Leaving directory `/usr/src/test/linux-2.6.29.5' I'm actually baffled where it got /usr/src/test/linux-2.6.29.5 from?? How did it even figure that out? In this case it was the original kernel dir I was using, but now I want to try compiling against the broken kernel tree? The thought occurs that this could be part of the problem I was seeing before...? Grateful for your thoughts? Ed W ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge
