On 23/10/2013 00:35, sf...@users.sourceforge.net wrote:
> Hello Ed,
>
> Ed W:
>> - apply ./aufs3-kbuild.patch to your kernel source files.
>> - apply ./aufs3-base.patch too.
>> - apply ./aufs3-proc_map.patch too,
>> - copy ./{Documentation,fs,include/uapi/linux/aufs_type.h} files to your
>>     kernel source tree.
>> - make
>>
>> So clarifying this, my "aufs_type.h" file *is* in include/uapi/linux/
>> and not in include/linux/ - is this correct?
> You need to run "make headers_install".
> It installs a modified version of ./include/uapi/linux/aufs_type.h as
> ./usr/include/linux/aufs_type.h
>
>
> J. R. Okajima

Thanks for the reply, however, without forcing it, this will put the 
files (as you say) into usr/include/linux/ - note the usr/ prefix?

Just to be clear - I'm having trouble compiling the kernel itself. 
Something in the compile wants a file
     include/linux/aufs_type.h
but I'm only copying across
     include/uapi/linux/aufs_type.h
(and then patching and calling make)

A grep of the code (excluding docs and large header_install line)

fs/aufs/Makefile:ccflags-y += -include ${M}/../../include/linux/aufs_type.h
fs/aufs/Makefile:ccflags-y += -include ${srctree}/include/linux/aufs_type.h
fs/aufs/branch.c:        * cf. AUFS_MAX_NAMELEN in include/linux/aufs_type.h
include/uapi/linux/Kbuild:header-y += aufs_type.h

So, to the eye it seems like the fs/aufs makefile wants to see the 
include file somehow get copied across from include/uapi/linux to 
include/linux - how does that process happen?

Note, I have quite probably broken the build process with some 
additional patches, but grateful for a leg up understanding what is 
*supposed* to be happening so that I can try and understand what!

Many thanks

Ed W

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk

Reply via email to