Re: [Valgrind-users] Help: Can't make Valgrind executable.

[Azat K. <a3a...@gm...>]

On Thu, Jan 22, 2015 at 10:07:58PM +0100, Florian Krohm wrote:
> > ----- 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

Also check you $PATH variable in bash:
$ echo $PATH

>From bash(1):
       PATH   The search path for commands.  It is a colon-separated list of directories in which the shell looks for commands (see COMMAND EXECUTION below).  A zero-length (null) directory name in the value of PATH indicates the current directory.  A null directory
              name may appear as two adjacent colons, or as an initial or trailing colon.  The default path is system-dependent, and is set by the administrator who installs bash.  A common value is ``/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin''.

IOW you $PATH must looks like:
/usr/local/bin:/usr/bin:/bin # maybe some sbin folders too

To find valgrind with default --prefix.

Cheers,
Azat.

> > 
> > 	. . .
> > 
> > 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.