|
From: Eyal L. <ey...@ey...> - 2004-01-25 22:48:31
|
Pawel Kot wrote: > > On Thu, 22 Jan 2004, Marcelo Tosatti wrote: > > > What happened to this? > > > > Was valgrind fixed or its compilation is still broken? > > I have successfully built valgrind versions 2.0.0 and 2.1.0 with 2.4.24 > includes. I have explicitely copied the includes from the sources to be > sure it is correct. > > pkot@laptok:~$ gcc -v > [...] > gcc version 3.2.2 Sure. The problem only started with 2.4.25-pre. It was clear from the start that linux headers changed. [BTW, it really started with 2.4.24-pre, but this series was withdrawn and became 2.4.25-pre, hence the 2.4.24 in the title which I now changed]. The question is "who is at fault"? Are we (vg) using kernel headers incorrectly and were now caught, or did the linux people really break their headers. Is any valgrind developer testing with 2.4.25-pre? This is not an area I am familiar with, it is best handled by a vg person who knows about the use of asm/timex.h. -- Eyal Lebedinsky (ey...@ey...) <http://samba.org/eyal/> |