|
From: Maurice v. d. P. <gri...@ge...> - 2005-07-29 17:46:15
|
On Wed, Jul 27, 2005 at 09:17:35PM +0100, Julian Seward wrote:
> Please download and test this release candidate, and let us know of
> any problems you encounter.
It compiles on one of my systems, but not on the other. The system that
it fails to build on is an nptl only system.
The build fails because of a few static const variable declarations
within functions. Why are these static? If I change them to normal const
variables, the compilation succeeds.
One example of this is in coregrind/m_aspacemgr/aspacemgr.c at the
beginning of function VG_(unmap_range). The error I get is
"initializer element is not constant".
I've tried with
compilers: gcc 3.3.3
gcc 3.4.3
gcc 3.4.4
glibc: 2.3.5
Attached is a patch to change all problematic static consts into consts.
Best regards,
Maurice.
P.S.: If proc is not mounted, valgrind exits like this:
open /proc/self/maps: No such file or directory
Segmentation fault
It would be nice if it could exit more gracefully.
--
Maurice van der Pot
Gentoo Linux Developer gri...@ge... http://www.gentoo.org
Creator of BiteMe! gri...@kf... http://www.kfk4ever.com
|