On 03/07/2010 09:25 PM, Antoine Martin wrote:
On 03/08/2010 02:17 AM, Avi Kivity wrote:
On 03/07/2010 09:13 PM, Antoine Martin wrote:
What version of glibc do you have installed?
Latest stable:
sys-devel/gcc-4.3.4
sys-libs/glibc-2.10.1-r1
$ git show glibc-2.10~108 | head
commit e109c6124fe121618e42ba882e2a0af6e97b8efc
Author: Ulrich Drepper <drep...@redhat.com>
Date: Fri Apr 3 19:57:16 2009 +0000
* misc/Makefile (routines): Add preadv, preadv64, pwritev,
pwritev64.
* misc/Versions: Export preadv, preadv64, pwritev, pwritev64 for
GLIBC_2.10.
* misc/sys/uio.h: Declare preadv, preadv64, pwritev, pwritev64.
* sysdeps/unix/sysv/linux/kernel-features.h: Add entries for
preadv
You might get away with rebuilding glibc against the 2.6.33 headers.
The latest kernel headers available in gentoo (and they're masked
unstable):
sys-kernel/linux-headers-2.6.32
So I think I will just keep using Christoph's patch until .33 hits
portage.
Unless there's any reason not to? I would rather keep my system "clean".
I can try it though, if that helps you clear things up?
preadv/pwritev was actually introduced in 2.6.30. Perhaps you last
build glibc before that? If so, a rebuild may be all that's necessary.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
