Just to let you know: I fixed the build process and aufs header file was correctly modified.
Thank you very much! Serge On 07/27/2011 08:48 PM, sf...@users.sourceforge.net wrote: > > kirk w: >> A question related to this. Normally if you replace the kernel headers you >> need to rebuild glibc, gcc ... Is it OK to install the kernel headers in a >> build environment so we can build the AUFS utils and then move those utils >> to a system built with different kernel headers? I've been assuming the >> answer is yes, it seems to work. > > "make headers_install" modifies the kernel header files to be usable > from userspace. For example, they may declare "char *p" as > "char __user *p" which means the address is in userspace instead of > kernelspace. This is important from kernel, but it has no meaning for > userspace. So "make headers_install" removes "__user" simply. > > All the changes by "make headers_install" should never affect glibc, > gcc, etc. So you don't have to rebuild them. You can just keep using it. > Of course it depends upon what "different kernel headers" means. In case > of different architectures including 32/64 bit, you need to rebuild and > use the correct version. > > > J. R. Okajima > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1
