> After extracting the tar'd files, I entered the "./configure" command, then
> "make", then "make install".
>
> *Then when I try to test it with "valgrind ls -l" I get: "-bash: valgrind:
> command not found".**
> *
> There's no file in the installation folder called simply "valgrind". (I'm
> expecting to find an executable file by this name.)
----- README
To install from a tar.bz2 distribution:
4. Run ./configure, with some options if you wish. The only interesting
one is the usual --prefix=/where/you/want/it/installed.
----- configure
ac_default_prefix=/usr/local
. . .
Installation directories:
--prefix=PREFIX install architecture-independent files in PREFIX
[$ac_default_prefix]
--exec-prefix=EPREFIX install architecture-dependent files in EPREFIX
[PREFIX]
By default, \`make install' will install all the files in
\`$ac_default_prefix/bin', \`$ac_default_prefix/lib' etc.
-----
So by default you should look for /usr/local/bin/valgrind .
Often you would put /usr/local/bin as one of the paths in your
$PATH shell environment variable.
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
