Re: [Valgrind-users] Error while running valgrind on different, machine than orignal place where it was compiled

[Julian S. <js...@ac...>]

On Monday 28 April 2008 13:10, Christian Keil wrote:
> > I had to compile Valgrind source code on a different host because I do
> > not have any compilation tools installed on my production host.
> >
> > I thought of using "-prefix=<Install-dir-path>" while doing
> > "./configure".
> >
> > But I cannot do that also because the directory structure on
> > production
> > host is totally different than development host (this is because user
> > logins are different).
>
> This is the scenario that DESTDIR is made for. Configure Valgrind
> exactly like you would do it when building on your production machine
> (i.e., use the prefix from that machine), make all, and then
>
> $ make install DESTDIR=temporary/install/prefix
>
> This way make will compile the correct paths into the library but copy
> the files to <temporary/install/prefix/...> from where you can just copy
> everything to your production machine.

Sounds good, but do you know if this really works with Valgrind?
I'm sure we "bake in" some paths at build time.

J