|
From: Bob R. <bob...@co...> - 2006-10-05 13:00:22
|
Hi,
I'm trying to compile valgrind svn with the omega patch. I just got this
error. Any ideas?
Thanks,
Bob Rossi
make all-recursive
make[1]: Entering directory `/home/USERS/bar/download/valgrind/valgrind'
Making all in include
make[2]: Entering directory `/home/USERS/bar/download/valgrind/valgrind/include'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/USERS/bar/download/valgrind/valgrind/include'
Making all in coregrind
make[2]: Entering directory `/home/USERS/bar/download/valgrind/valgrind/coregrind'
make all-am
make[3]: Entering directory `/home/USERS/bar/download/valgrind/valgrind/coregrind'
make -C ../VEX pub/libvex_guest_offsets.h
make[4]: Entering directory `/home/USERS/bar/download/valgrind/valgrind/VEX'
make[4]: `pub/libvex_guest_offsets.h' is up to date.
make[4]: Leaving directory `/home/USERS/bar/download/valgrind/valgrind/VEX'
for f in vgpreload_core-x86-linux.so ; do \
p=`echo $f | sed -e 's/^[^-]*-//' -e 's/\..*$//'`; \
n=`echo $f | sed -e 's/-[^-]\{1,\}-[^-.]\{1,\}//'`; \
mkdir -p ../.in_place/$p; \
rm -f ../.in_place/$p/$n; \
ln -f -s ../../coregrind/$f ../.in_place/$p/$n; \
done
make[3]: Leaving directory `/home/USERS/bar/download/valgrind/valgrind/coregrind'
make[2]: Leaving directory `/home/USERS/bar/download/valgrind/valgrind/coregrind'
Making all in .
make[2]: Entering directory `/home/USERS/bar/download/valgrind/valgrind'
mkdir -p ./.in_place
rm -f ./.in_place/default.supp ./.in_place/glibc-2.2.supp ./.in_place/glibc-2.3.supp ./.in_place/glibc-2.4.supp ./.in_place/xfree-3.supp ./.in_place/xfree-4.supp
ln -s ../default.supp ./.in_place
ln -s .././glibc-2.2.supp .././glibc-2.3.supp .././glibc-2.4.supp .././xfree-3.supp .././xfree-4.supp ./.in_place
make[2]: Leaving directory `/home/USERS/bar/download/valgrind/valgrind'
Making all in tests
make[2]: Entering directory `/home/USERS/bar/download/valgrind/valgrind/tests'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/USERS/bar/download/valgrind/valgrind/tests'
Making all in perf
make[2]: Entering directory `/home/USERS/bar/download/valgrind/valgrind/perf'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/USERS/bar/download/valgrind/valgrind/perf'
Making all in auxprogs
make[2]: Entering directory `/home/USERS/bar/download/valgrind/valgrind/auxprogs'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/USERS/bar/download/valgrind/valgrind/auxprogs'
Making all in memcheck
make[2]: Entering directory `/home/USERS/bar/download/valgrind/valgrind/memcheck'
Making all in .
make[3]: Entering directory `/home/USERS/bar/download/valgrind/valgrind/memcheck'
make -C ../VEX CC="gcc" libvex_x86_linux.a \
EXTRA_CFLAGS=" -mpreferred-stack-boundary=2 -O -g -Wmissing-prototypes -Winline -Wall -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations "
make[4]: Entering directory `/home/USERS/bar/download/valgrind/valgrind/VEX'
gcc -Wall -Wmissing-prototypes -Wshadow -Winline -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wcast-align -Wmissing-declarations -mpreferred-stack-boundary=2 -O -g -Wmissing-prototypes -Winline -Wall -Wshadow -Wpointer-arith -Wstrict-prototypes -Wmissing-declarations -g -O2 -Ipub -Ipriv -o priv/main/vex_main.o \
-c priv/main/vex_main.c
In file included from priv/main/vex_main.c:86:
priv/main/vex_svnversion.h:1:1: missing terminating " character
priv/main/vex_svnversion.h:1:1: warning: no newline at end of file
make[4]: *** [priv/main/vex_main.o] Error 1
make[4]: Leaving directory `/home/USERS/bar/download/valgrind/valgrind/VEX'
make[3]: *** [../VEX/libvex_x86_linux.a] Error 2
make[3]: Leaving directory `/home/USERS/bar/download/valgrind/valgrind/memcheck'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/USERS/bar/download/valgrind/valgrind/memcheck'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/USERS/bar/download/valgrind/valgrind'
make: *** [all] Error 2
|
|
From: James Y. <jam...@gm...> - 2011-11-22 14:10:04
|
The error shown directly below resuls almost immediately after I run the program. I am used to using Valgrind 3.6.1 and I believe this is a existing and unsolved error. I am no using Valgrind 3.7.0 and the results are the same. A search of the web came upo with some patch files, That claim can fix this problem. Do they actually work? Is there a fix out there for this. I tried binutils-gold (latestest version) and it did not fix this error. If there is a fix where can I find it? James M. Yunker james@james-Precision-WorkStation-T7500:~/Desktop/WEGtestOpt$ valgrind --tool=memcheck ./grab_gcc_debug valgrind: mmap(0x8062000, 858030080) failed in UME with error 22 (Invalid argument). valgrind: this can be caused by executables with very large text, data or bss segments. |
|
From: Julian S. <js...@ac...> - 2006-10-05 13:05:47
|
> priv/main/vex_svnversion.h:1:1: missing terminating " character > priv/main/vex_svnversion.h:1:1: warning: no newline at end of file (cd VEX && make version) && make J |
|
From: Bob R. <bob...@co...> - 2006-10-05 13:21:58
|
On Thu, Oct 05, 2006 at 02:05:33PM +0100, Julian Seward wrote: > > > priv/main/vex_svnversion.h:1:1: missing terminating " character > > priv/main/vex_svnversion.h:1:1: warning: no newline at end of file > > (cd VEX && make version) && make Apparently you can't build valgrind if subversion is not on your path. Is this a known issue? Thanks, Bob Rossi |
|
From: Julian S. <js...@ac...> - 2006-10-05 13:36:54
|
On Thursday 05 October 2006 14:21, Bob Rossi wrote:
> On Thu, Oct 05, 2006 at 02:05:33PM +0100, Julian Seward wrote:
> > > priv/main/vex_svnversion.h:1:1: missing terminating " character
> > > priv/main/vex_svnversion.h:1:1: warning: no newline at end of file
> >
> > (cd VEX && make version) && make
>
> Apparently you can't build valgrind if subversion is not on your path.
> Is this a known issue?
The deal is: if you are building from an svn checkout then you
are assumed to be a developer and so you need svn, svnversion,
automake, autoconf to be available, not to mention tons of ugly
XML toolchain gunk if you want to build the documentation.
If you are building from a tarball you are assumed to be an end-user
and none of those things are required for the build; everything
needed is baked into the tarball at tarball-creation ("make dist")
time.
J
|
|
From: Bob R. <bob...@co...> - 2006-10-05 13:38:54
|
On Thu, Oct 05, 2006 at 02:36:39PM +0100, Julian Seward wrote:
>
> On Thursday 05 October 2006 14:21, Bob Rossi wrote:
> > On Thu, Oct 05, 2006 at 02:05:33PM +0100, Julian Seward wrote:
> > > > priv/main/vex_svnversion.h:1:1: missing terminating " character
> > > > priv/main/vex_svnversion.h:1:1: warning: no newline at end of file
> > >
> > > (cd VEX && make version) && make
> >
> > Apparently you can't build valgrind if subversion is not on your path.
> > Is this a known issue?
>
> The deal is: if you are building from an svn checkout then you
> are assumed to be a developer and so you need svn, svnversion,
> automake, autoconf to be available, not to mention tons of ugly
> XML toolchain gunk if you want to build the documentation.
>
> If you are building from a tarball you are assumed to be an end-user
> and none of those things are required for the build; everything
> needed is baked into the tarball at tarball-creation ("make dist")
> time.
OK, that's fair enough. I happened to check out valgrind like
PATH=/home/TOOLS/subversion/bin:$PATH svn co ...
and then make failed. It might be helpful to have a configure
check to make sure the svn tools required are on the path. However, it's
just a suggestion, and understand if no one wants to do that ...
Bob Rossi
|