The problem is that 'make headers_install' does not install aufs_type.h
anywhere, as far as I know.
Probably the aufs3-kbuild.patch should add one line to
$LinuxSrc/include/uapi/linux/Kbuild as follows?
header-y += aufs_type.h
Thank you
Tomas M
On Sat, Mar 9, 2013 at 2:03 PM, <[1]sf...@users.sourceforge.net> wrote:
Tomas M:
> I've compiled aufs (standalone) for Linux 3.8.2, and I've copied file
> aufs_type.h from Linux tree to /usr/include/linux/aufs_type.h
> When that was done, I wanted to compile aufs utils, but 'make' returned an
> error:
>
> cc -I./libau -O -Wall -DMOUNT_CMD_PATH=\"\" ver.c -o ver
> In file included from ver.c:19:0:
> /usr/include/linux/aufs_type.h:180:27: error: expected :, ,, ;, } or
> __attribute__ before * token
> make: *** [ver] Error 1
The released aufs_type.h file is for kernel-space only and you cannot
use it for user-space.
To use it in user-space (eg. aufs-util),
- run "make headers_install" in your kernel source tree
or
run "make install_header" in your aufs3-standalone source tree,
then new $PWD/usr/include/linux/aufs_type.h file will be generated.
- when compiling aufs-util, you need to specify the path to aufs_type.h,
for example,
CPPFLAGS="-I $LinuxSrc/usr/include -I $AufsStdalone/usr/include"
J. R. Okajima
References
1. mailto:sf...@users.sourceforge.net
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
