Thomas Sachau: > You seem to execute scripts/Makefile.headerinst inside the kernel source = > dir, which operates inside > the kernel source dir, but of course has not access right there.
So you need to run "make headers_install" BEFORE building aufs. > That may be possible, but the encouraged and most common way is to instal= > l a package called > "kernel-headers" instead of installing headers from the kernel sources an= > d i have those kernel > headers installed. They of course dont install any aufs2 specific headers= headers_install modifies some kernel header files. For instance, remove #ifdef __KERNEL__ ... #endif section, remove __user modifier, etc. And these operations are also necessary to include/linux/aufs_type.h. In building aufs2-standalone, aufs Makefile tries creating aufs_type.h which is usable from userspace by using Makefile.headerinst. If you have never run Makefile.headerinst, then make(1) MAY create/remove some temporary files and it MAY be the cause of your first problem. In building aufs2-util, the build process refers the kernel header files (including aufs_type.h) which should be already handled by Makefile.headerinst. J. R. Okajima ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev
