|
From: Cao, L. \(STP\) <Lih...@gu...> - 2005-08-09 22:41:42
|
I downloaded the source code for 3.0 and tried to build on my Redhat 7.3 = box. I got the following errors during "make" make all-recursive make[1]: Entering directory `/root/valgrind-3.0.0' Making all in include make[2]: Entering directory `/root/valgrind-3.0.0/include' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/root/valgrind-3.0.0/include' Making all in coregrind make[2]: Entering directory `/root/valgrind-3.0.0/coregrind' make all-recursive make[3]: Entering directory `/root/valgrind-3.0.0/coregrind' Making all in m_aspacemgr make[4]: Entering directory `/root/valgrind-3.0.0/coregrind/m_aspacemgr' if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../coregrind -I../.. = -I../../coregrind/x86 -I../../coregrind/linux = -I../../coregrind/x86-linux -I../../include = -I/root/valgrind-3.0.0/VEX/pub -DVGA_x86=3D1 -DVGO_linux=3D1 = -DVGP_x86_linux=3D1 -mpreferred-stack-boundary=3D2 = -Wmissing-prototypes -Winline -Wall -Wshadow -O -g -Wno-long-long -MT = aspacemgr.o -MD -MP -MF ".deps/aspacemgr.Tpo" -c -o aspacemgr.o = aspacemgr.c; \ then mv -f ".deps/aspacemgr.Tpo" ".deps/aspacemgr.Po"; else rm -f = ".deps/aspacemgr.Tpo"; exit 1; fi aspacemgr.c: In function `vgPlain_setup_pointercheck': aspacemgr.c:1284: parse error before `ldt' aspacemgr.c:1296: `ret' undeclared (first use in this function) aspacemgr.c:1296: (Each undeclared identifier is reported only once aspacemgr.c:1296: for each function it appears in.) make[4]: *** [aspacemgr.o] Error 1 make[4]: Leaving directory `/root/valgrind-3.0.0/coregrind/m_aspacemgr' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/root/valgrind-3.0.0/coregrind' make[2]: *** [all] Error 2 make[2]: Leaving directory `/root/valgrind-3.0.0/coregrind' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/valgrind-3.0.0' make: *** [all] Error 2 Can anyone help? Thanks a lot, Lihong Cao |
|
From: Tom H. <to...@co...> - 2005-08-09 22:52:19
|
In message <A05FF83D58C85A48B56626C432CFB2C12E726A@STPEVS02.stp.guidant.com>
"Cao, Lihong (STP)" <Lih...@gu...> wrote:
> I downloaded the source code for 3.0 and tried to build on my Redhat 7.3 box.
[ snipped ]
> aspacemgr.c: In function `vgPlain_setup_pointercheck':
> aspacemgr.c:1284: parse error before `ldt'
> aspacemgr.c:1296: `ret' undeclared (first use in this function)
> aspacemgr.c:1296: (Each undeclared identifier is reported only once
> aspacemgr.c:1296: for each function it appears in.)
That's a bug - the code is declaring a variable in the middle of
a function instead of at the start. That is allowed in modern
compilers which support C99 but not in an old compiler like the
one RH73 is using.
Please file a bug for this in the bug tracker.
Thanks,
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Julian S. <js...@ac...> - 2005-08-09 22:53:21
|
You can build and use 3.0.0 on RH7.3 (I tested it myself, and so did Tom) but you can't use the default gcc-2.96 compiler to build it with. I have been using gcc-3.0.4 on RH7.3 and that appears to build Valgrind with no problems. J On Tuesday 09 August 2005 23:41, Cao, Lihong (STP) wrote: > I downloaded the source code for 3.0 and tried to build on my Redhat 7.3 > box. > > I got the following errors during "make" > > make all-recursive > make[1]: Entering directory `/root/valgrind-3.0.0' > Making all in include > make[2]: Entering directory `/root/valgrind-3.0.0/include' > make[2]: Nothing to be done for `all'. > make[2]: Leaving directory `/root/valgrind-3.0.0/include' > Making all in coregrind > make[2]: Entering directory `/root/valgrind-3.0.0/coregrind' > make all-recursive > make[3]: Entering directory `/root/valgrind-3.0.0/coregrind' > Making all in m_aspacemgr > make[4]: Entering directory `/root/valgrind-3.0.0/coregrind/m_aspacemgr' > if gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../coregrind -I../.. > -I../../coregrind/x86 -I../../coregrind/linux -I../../coregrind/x86-linux > -I../../include -I/root/valgrind-3.0.0/VEX/pub -DVGA_x86=1 -DVGO_linux=1 > -DVGP_x86_linux=1 -mpreferred-stack-boundary=2 -Wmissing-prototypes > -Winline -Wall -Wshadow -O -g -Wno-long-long -MT aspacemgr.o -MD -MP -MF > ".deps/aspacemgr.Tpo" -c -o aspacemgr.o aspacemgr.c; \ then mv -f > ".deps/aspacemgr.Tpo" ".deps/aspacemgr.Po"; else rm -f > ".deps/aspacemgr.Tpo"; exit 1; fi aspacemgr.c: In function > `vgPlain_setup_pointercheck': > aspacemgr.c:1284: parse error before `ldt' > aspacemgr.c:1296: `ret' undeclared (first use in this function) > aspacemgr.c:1296: (Each undeclared identifier is reported only once > aspacemgr.c:1296: for each function it appears in.) > make[4]: *** [aspacemgr.o] Error 1 > make[4]: Leaving directory `/root/valgrind-3.0.0/coregrind/m_aspacemgr' > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory `/root/valgrind-3.0.0/coregrind' > make[2]: *** [all] Error 2 > make[2]: Leaving directory `/root/valgrind-3.0.0/coregrind' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/root/valgrind-3.0.0' > make: *** [all] Error 2 > > Can anyone help? Thanks a lot, > > Lihong Cao > > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |
|
From: Tom H. <to...@co...> - 2005-08-09 22:59:05
|
In message <200...@ac...>
Julian Seward <js...@ac...> wrote:
> You can build and use 3.0.0 on RH7.3 (I tested it myself, and
> so did Tom) but you can't use the default gcc-2.96 compiler to
> build it with. I have been using gcc-3.0.4 on RH7.3 and that
> appears to build Valgrind with no problems.
The box I do the overnight RH73 builds on is using gcc 3.2.2 now
which is why those work. Like you say, the standard RH73 compiler
won't work as it require variable declarations to be at the start
of blocks.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Julian S. <js...@ac...> - 2005-08-09 23:15:55
|
> > You can build and use 3.0.0 on RH7.3 (I tested it myself, and > > so did Tom) but you can't use the default gcc-2.96 compiler to > > build it with. I have been using gcc-3.0.4 on RH7.3 and that > > appears to build Valgrind with no problems. > > The box I do the overnight RH73 builds on is using gcc 3.2.2 now > which is why those work. Like you say, the standard RH73 compiler > won't work as it require variable declarations to be at the start > of blocks. To tell the whole truth .. it was in fact me who introduced most of these variable declarations in the middle of blocks. They are very convenient after all. For a long time it was fine, but when I built it on RH73 with gcc-2.96, it died. And I was too lazy to fix it; downloading/installing gcc-3.0.4 was easier :-) I did have a go, but gave up when I realised it would be several hours work. Also ... I remember getting into a pickle with gcc-2.96 and the order of qualifiers for __attribute__((regparm)) on fn declarations. That was another motivation for upgrading the compiler rather than spending time how to write gcc-2.96 compatible regparm incantations. Neither of which are very honourable motivations .. J |
|
From: Igmar P. <mai...@jd...> - 2005-08-10 07:15:21
|
> Also ... I remember getting into a pickle with gcc-2.96 and the > order of qualifiers for __attribute__((regparm)) on fn declarations. > That was another motivation for upgrading the compiler rather > than spending time how to write gcc-2.96 compatible regparm > incantations. Not to mention that gcc 2.96 is know to misbehave in a number of cases. Numerous projects refuse to compile if 2.96 is used. Igmar |