|
From: <ar...@de...> - 2003-11-03 15:56:34
Attachments:
valgrind-2.6-headers-fixes.patch
|
Hi all. I've been maintaining valgrind for Debian using 2.4 kernel series. Debian glibc maintainers have included now glibc packages compiled with linux 2.6 headers and then valgrind compilation stop working. The problem is that valgrind includes kernel headers directly instead of make a local copy of those constants and definitions on the valgrind headers. I've attached a patch that solves the problem (for the moment) and I was able to recompile valgrind again. However, it would be good to re-evaluate the way valgrind includes its files. Thanks for the good work so far :) |
|
From: Jeremy F. <je...@go...> - 2003-11-03 17:08:00
|
On Mon, 2003-11-03 at 07:56, Andrés Roldán wrote: > Hi all. > > I've been maintaining valgrind for Debian using 2.4 kernel series. > > Debian glibc maintainers have included now glibc packages compiled with > linux 2.6 headers and then valgrind compilation stop working. > > The problem is that valgrind includes kernel headers directly instead > of make a local copy of those constants and definitions on the valgrind > headers. We seem to be moving in that direction anyway (see the addition of vg_unistd.h). vg_unsafe.h is a bit of a mess, and it will continue to bite us - but copying a minimal subset of the kernel headers (and maybe doing a vg/vki transform on them) is a moderately tedious editoral job which nobody has taken up yet. J |