On Fri, Jan 29, 2016 at 11:49:29PM -0500, Pranith Kumar wrote:
On Fri, Jan 29, 2016 at 11:41 PM, Theodore Ts'o [off-list ref] wrote:
quoted
So on my Debain system, I don't update linux-libc-dev when I install a
new upstream kernel built using "make deb-pkg". I'll still a new
version of the linux-image-*.deb file, and maybe a newer version of
linux-firmware-*.dev, but I don't bother installing the
linux-headers-*.deb file (since I don't compile external kernel
modules), and I don't bother installing linux-libc-dev-*.deb (because
of situations like this, where the userspace include files need ot be
updated in sync, and this should be the distribution's problem to
handle).
I am using a debian system and built the kernel using
"make bindeb-pkg". This generated the following debs:
linux-firmware-image-4.5.0-rc1+_4.5.0-rc1+-2_powerpc.deb
linux-image-4.5.0-rc1+_4.5.0-rc1+-2_powerpc.deb
linux-headers-4.5.0-rc1+_4.5.0-rc1+-2_powerpc.deb
linux-libc-dev_4.5.0-rc1+-2_powerpc.deb
which I installed as I usually do to test new system calls or run other tests.
I'll try to update the uapi header files manually and see how it goes...
You need to update qemu's autoconf to define HAVE_FSXATTR if it's
found in the uapi/linux/fs.h so that it then isn't defined in
xfs/xfs_fs.h.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com