|
From: Mads J. <mad...@mo...> - 2005-12-07 12:30:24
|
Hi I have tried to install valgrind to a non default path: ./configure --prefix some-path make all make install There is no problem in the x86 instalation, but for the amd64-linux I get the following error message: valgrind: failed to start tool 'memcheck' for platform 'amd64-linux': No such file or directory Memcheck is located at ../lib/valgrind/amd64-linux/ relative to the bin directory. Which is the same relative path as x86-linux. Have any of you had simulare problems ? best regards, Mads |
|
From: Dirk M. <dm...@gm...> - 2005-12-07 13:34:14
|
On Wednesday 07 December 2005 13:29, Mads Jepsen wrote: > Memcheck is located at ../lib/valgrind/amd64-linux/ relative to the bin > directory. Which is the same relative path as x86-linux. it should have been installed in ../lib64/... Dirk |
|
From: Vikram N. <vik...@ya...> - 2005-12-08 07:31:40
|
Dirk Mueller <dmuell <at> gmx.net> writes: > > On Wednesday 07 December 2005 13:29, Mads Jepsen wrote: > > Memcheck is located at ../lib/valgrind/amd64-linux/ relative to the bin > > directory. Which is the same relative path as x86-linux. > it should have been installed in ../lib64/... > > Dirk Hi, I am also facing a similar problem. I renamed lib to lib64 but it still does not work. Now, Memcheck is at ../lib64/valgrind/amd64-linux/ relative to bin folder. Could you please let me know it anything else needs to be changed? Thanks, Vikram |
|
From: Tom H. <to...@co...> - 2005-12-11 14:59:24
|
In message <200...@gm...>
Dirk Mueller <dm...@gm...> wrote:
> On Wednesday 07 December 2005 13:29, Mads Jepsen wrote:
>
> > Memcheck is located at ../lib/valgrind/amd64-linux/ relative to the bin
> > directory. Which is the same relative path as x86-linux.
>
> it should have been installed in ../lib64/...
Not necessarily - configuring by hand will use lib on most systems
and some distributions don't use lib64 at all.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Tom H. <to...@co...> - 2005-12-11 14:57:33
|
In message <1133958570.25925.34.camel@localhost.localdomain>
Mads Jepsen <mad...@mo...> wrote:
> I have tried to install valgrind to a non default path:
> ./configure --prefix some-path
> make all
> make install
> There is no problem in the x86 instalation, but for the amd64-linux I
> get the following error message:
> valgrind: failed to start tool 'memcheck' for platform 'amd64-linux': No
> such file or directory
>
> Memcheck is located at ../lib/valgrind/amd64-linux/ relative to the bin
> directory. Which is the same relative path as x86-linux.
Can I ask you to clarify exactly how you built and installed
valgrind? Did you build it once on an amd64 box or did you try and
build it twice, once for x86 and once for amd64 and then install
them both on the same box?
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Mads J. <mad...@mo...> - 2005-12-12 07:30:47
|
I only build it once on the amd64 box and then installed it there. Mads On Sun, 2005-12-11 at 14:57 +0000, Tom Hughes wrote: > In message <1133958570.25925.34.camel@localhost.localdomain> > Mads Jepsen <mad...@mo...> wrote: > > > I have tried to install valgrind to a non default path: > > ./configure --prefix some-path > > make all > > make install > > There is no problem in the x86 instalation, but for the amd64-linux I > > get the following error message: > > valgrind: failed to start tool 'memcheck' for platform 'amd64-linux': No > > such file or directory > > > > Memcheck is located at ../lib/valgrind/amd64-linux/ relative to the bin > > directory. Which is the same relative path as x86-linux. > > Can I ask you to clarify exactly how you built and installed > valgrind? Did you build it once on an amd64 box or did you try and > build it twice, once for x86 and once for amd64 and then install > them both on the same box? > > Tom |
|
From: Tom H. <to...@co...> - 2005-12-12 17:28:43
|
In message <1134372564.23613.7.camel@localhost.localdomain>
Mads Jepsen <mad...@mo...> wrote:
> I only build it once on the amd64 box and then installed it there.
Can you run valgrind under strace and see what you get - something
like this:
strace -o strace.out valgrind --tool=memcheck date
and then send in the strace.out file error.
> On Sun, 2005-12-11 at 14:57 +0000, Tom Hughes wrote:
> > In message <1133958570.25925.34.camel@localhost.localdomain>
> > Mads Jepsen <mad...@mo...> wrote:
> >
> > > I have tried to install valgrind to a non default path:
> > > ./configure --prefix some-path
> > > make all
> > > make install
> > > There is no problem in the x86 instalation, but for the amd64-linux I
> > > get the following error message:
> > > valgrind: failed to start tool 'memcheck' for platform 'amd64-linux': No
> > > such file or directory
> > >
> > > Memcheck is located at ../lib/valgrind/amd64-linux/ relative to the bin
> > > directory. Which is the same relative path as x86-linux.
> >
> > Can I ask you to clarify exactly how you built and installed
> > valgrind? Did you build it once on an amd64 box or did you try and
> > build it twice, once for x86 and once for amd64 and then install
> > them both on the same box?
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Fernando M. S. <fc...@ne...> - 2007-03-20 22:36:00
|
Tom Hughes <tom <at> compton.nu> writes: > > In message <1134372564.23613.7.camel <at> localhost.localdomain> > Mads Jepsen <mads.jepsen <at> mosek.com> wrote: > > > I only build it once on the amd64 box and then installed it there. > In perf/tinycc.c after tcc_add_library_path(s, "/usr/local/lib"); tcc_add_library_path(s, "/usr/lib"); tcc_add_library_path(s, "/lib"); add tcc_add_library_path(s, "[myprefix]/lib"); rgds -- fernando |