|
From: Neil Y. <gm...@yo...> - 2005-08-15 09:11:18
|
valgrind is failing to compile with these errors
gcc -g -O -Wall -Wmissing-prototypes -Wshadow -Winline -Wpointer-arith
-Wbad-function-cast -Wcast-qual -Wcast-align -Wmissing-declarations -Ipub
-Ipriv -o priv/host-ppc32/isel.o \
-c priv/host-ppc32/isel.c
priv/host-ppc32/isel.c: In function `iselCondCode_wrk':
priv/host-ppc32/isel.c:1682: parse error before `*'
priv/host-ppc32/isel.c:1684: `ri2' undeclared (first use in this function)
priv/host-ppc32/isel.c:1684: (Each undeclared identifier is reported only once
priv/host-ppc32/isel.c:1684: for each function it appears in.)
I'm compiling using g++-3.4.4 on RedHat 7.3
The error occurs on the line
PPC32RH* ri2 = iselIntExpr_RH(env, syned, e->Iex.Binop.arg2);
I can't see any obvious errors.
I've used gcc -E to check that it is pulling in the definition of PPC32RH from
the headers.
Has anyone else seen this error?
Neil Youngman
|
|
From: Neil Y. <gm...@yo...> - 2005-08-15 09:45:58
|
Neil Youngman <gmane <at> youngman.org.uk> writes: > > I'm compiling using g++-3.4.4 on RedHat 7.3 I've just realised that although I've configured it wrih CC=gcc-3.4.4, it isn't using gcc-3.4.4, so the declaration in the middle of the block is confusing it. If it doesn't use CC from configure, I need to figure out how to get it to use the correct version of gcc. Neil Youngman |
|
From: Neil Y. <gm...@yo...> - 2005-08-15 09:55:30
|
Neil Youngman <gmane <at> youngman.org.uk> writes: > > Neil Youngman <gmane <at> youngman.org.uk> writes: > > > > > I'm compiling using g++-3.4.4 on RedHat 7.3 > > I've just realised that although I've configured it wrih CC=gcc-3.4.4, it isn't > using gcc-3.4.4, so the declaration in the middle of the block is confusing it. > If it doesn't use CC from configure, I need to figure out how to get it to use > the correct version of gcc. The problem seems to be that valgrind-3.0.0/VEX/Makefile has CC=gcc, although it was set to gcc-3.4.4 in the configuration. Changing it in this Makefile allows valgrind to build. This seems to be a deficiency in the configuration script. Neil Youngman |
|
From: Nicholas N. <nj...@cs...> - 2005-08-17 02:53:28
|
On Mon, 15 Aug 2005, Neil Youngman wrote: > The problem seems to be that valgrind-3.0.0/VEX/Makefile has CC=gcc, > although it was set to gcc-3.4.4 in the configuration. Changing it in > this Makefile allows valgrind to build. > > This seems to be a deficiency in the configuration script. Yes. Vex has a hand-written Makefile, it does not use the automake/autoconf stuff that the rest of Valgrind does. The two options I can see are: - import CC from the configure script in the way that causes the minimum disturbance (I don't know how to do that, though) - fully automake/autoconf-ify Vex. The latter is made trickier by Vex being an SVN external module. Tom, do you know what would be a good way to fix this problem? N |