Thomas Sachau:
> > So you need to run "make headers_install" BEFORE building aufs.
>
> No. There is a package for those headers, which installs those prepared h=
> eaders. No package should
> ever install any files anywhere except the current builddir or any explic=
> itly named DESTDIR. That
> call would install many header files without any version control by any p=
> ackage manager, so you will
> also not be able to uninstall those headers properly.
??
If you don't specify INSTALL_HDR_PATH to "make headers_install", the
files will be created under ${linux-src}/usr/include. You can handle
them like *.o, eg. you don't need to uninstall or version control for them.
Additionally "make headers_install" compiles linux/scripts/unifdef which
will be necessary to create usr/include/linux/aufs_type.h.
You might be asserting that kernel-headers package is installed and it
should be enough. But building a kernel module requires some internal
scripts, commands or makefiles in kernel source tree. In other words,
while I am talking about "process" or headers_install, you are talking
about "result" of it.
I just looked at linux/scripts/Kbuild.include and found $(TMPOUT) make
variable. It may be one cause of your problem. I'd suggest you to give
this make-var to your build process.
> You should not rely on this external Makefile, since it does create other=
> issues, like this one.
> Please either create your own Makefile lines to create the header or incl=
> ude a stripped down version
> of the kernel Makefile with aufs2.
Hmm, it is hard for me to agree. I think we can trust any files in
kernel source tree even the files under scripts sub-dir.
But I agree that all output files can be outside of kernel tree if
necessary. Try $(TMPOUT).
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
