valgrind-users

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

[Alan B. <aba...@sy...>]

Hello,

I've followed the installation directions over and over, and still can't 
get a Valgrind executable.

(My experience up to this point has been on Windows, so I may be 
overlooking something simple.)

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

There are four files that start with "valgrind" and have suffixes such 
as "in", "spec", and "pc".

Linux version: Linux PS-EC3-APP1d.us.pressganey.com 
2.6.32-504.e16.x86_64 #1
SMP Wed Oct 15 04:27:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Any ideas what I can look at/test to get an idea what's going wrong?

Thanks,
Alan

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

[John R. <jr...@bi...>]

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

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

[Florian K. <fl...@ei...>]

On 22.01.2015 21:21, John Reiser wrote:
>> 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".**
>> *

Most likely "make install" did not succeed unless you ran it as root.
Regular users typically don't have write permissions in /usr/local which
is the default install point fro valgrind.
As John suggested use --prefix=........ when configuring. e.g.
./configure --prefix=/tmp/whatever
make && make install
/tmp/whatever/bin/valgrind ls -l

   Florian


>> 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
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
> 

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.