Hello everyone, beware, I found a problem with the approach I was trying to do.
In general I thought that in order to get the aufs_type.h installed in my system, I could simply do make headers_install with INSTALL_HDR_PATH=/usr I thought that this installs the header files in /usr/include and nothing more. But I was wrong. It seems it has bad side effects. For me, it removes essential files from the destination directory, like /usr/include/stdio.h and others... So I suggest everyone avoid this approach at all. Just use make headers_install and let it go to ./usr (a directory within linux kernel tree) and then copy the prepared aufs_type.h manually to the system includes. Tomas M On Sun, Aug 19, 2012 at 7:44 PM, Tomas M <to...@slax.org> wrote: >> But let me make sure again. >> Did you choose the first method or second? >> DESTDIR is for the second method only. > > Actually I used the first method (aufs in kernel, not a module). But I > believe that I will need aufs_type.h in my /usr/include/linux in order > to compile aufs-utils, regardless of which method I choose, so I need > make headers_install with INSTALL_HDR_PATH=/usr in both cases. Am I > wrong? > >> I wrote "copty ./usr/include/linux/aufs_type.h to ...", which means > > Ah, I didn't notice the leading dot in ./usr > > > Tomas M ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
