|
From: Oliver S. <ol...@f-...> - 2010-02-16 21:16:00
|
Alright, I got it to build by using a dirty trick. I did test this up
front with a single goal from the make file and then with all.
Before running "./configure" I did this from inside the source directory:
find -name 'Makefile.in' -exec sed -i 's/cd \$\$subdir/cd
\$(CURDIR)\/\$\$subdir/' {} \;
The idea is to make all occurrences of of 'cd $$subdir' in all
Makefile.in files absolute paths instead of the (default) relative
directory. Strangely enough this does the job. But it is still odd that
make would act up, since the "pwd" output from my previous post clearly
showed that the current directory was the correct one ...
But it's beyond me why "cd" failed. Anyway, perhaps this line above (no
line breaks, though) will help others having similar issues (remember to
call ./configure after it, though) ...
// Oliver
On 2010-02-16 20:24, Oliver Schneider wrote:
> Hello everybody,
>
> I've been trying to build Valgrind on my Debian (5.0.3) box, since the
> --read-var-info option doesn't seem to be in the version that comes via
> APT (which identifies as "valgrind-3.3.1-Debian").
>
> Running "./configure --prefix=$HOME/bin" doesn't give any errors, but
> once I start "make" it bombs out as follows:
>
> -----
> $ make
> echo "# This is a generated file, composed of the following suppression
> rules:"> default.supp
> echo "# " exp-ptrcheck.supp xfree-3.supp xfree-4.supp glibc-2.X-drd.supp
> glibc-2.34567-NPTL-helgrind.supp glibc-2.X.supp>> default.supp
> cat exp-ptrcheck.supp xfree-3.supp xfree-4.supp glibc-2.X-drd.supp
> glibc-2.34567-NPTL-helgrind.supp glibc-2.X.supp>> default.supp
> make all-recursive
> make[1]: Entering directory `/home/oliver/valgrind-3.5.0'
> Making all in include
> /bin/sh: line 17: cd: include: No such file or directory
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/oliver/valgrind-3.5.0'
> make: *** [all] Error 2
> -----
> [...]
|