|
From: Maurice v. d. P. <gri...@ge...> - 2005-07-29 18:17:42
|
On Fri, Jul 29, 2005 at 06:58:43PM +0100, Tom Hughes wrote: > > 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. >=20 > The problem is not the fact that it is static, but the fact that > the initialiser is invalid. I'd like to understand this. The initialiser is False || somestaticconstfil= evar.=20 Why would that be a problem only for static consts and not for consts?=20 What is the difference between static consts and consts within functions=20 for that matter? > For production use I would suggest that you probably want to have > optimisation turned on when building valgrind You're right. I forgot to check this. > There is already a bug on the bug tracker for this. You probably > want to attach yourself to it and maybe add your patch. Oh man! I'm the one who submitted the report! When I saw this problem this time I knew I had seen it before, but I searched through Gentoo's bugzilla and any patches I ever applied to my packages and didn't find anything.=20 Sorry for the duplicate report. I attached the patch to the bug report. Thanks, Maurice. --=20 Maurice van der Pot Gentoo Linux Developer gri...@ge... http://www.gentoo.org Creator of BiteMe! gri...@kf... http://www.kfk4ever.com |