|
From: Tom H. <to...@co...> - 2005-08-28 15:52:45
|
In message <Pin...@ch...>
Nicholas Nethercote <nj...@cs...> wrote:
> On Sun, 28 Aug 2005, Tom Hughes wrote:
>
> > What I'm thinking is to create x86-linux and amd64-linux subdirectories
> > under the normal valgrind library directory, move all the static tool
> > executables and the preload libraries there so we have two copies and
> > then get the launcher to choose the right ones.
>
> Is the normal approach to have lib/ and lib64/ directories? And maybe
> bin/ and bin64/ directories? If that's the standard approach we should
> follow it.
Well it is (although not universal - at least one linux distro has
not gone that way for amd64). This is actually a bit different though...
What we're specifying here is not the architecture that valgrind is
complied to run on (ie lib vs lib64) but the architecture of the binaries
a given tool is designed to run. There is (in principle) nothing to
prevent have a /usr/lib64/valgrind/solaris-sparc/memcheck tool on an
amd64 linux box if we ever got to the point of being able to do cross
platform/os emulation.
In other words it is more like the directories under /usr/lib/gcc
which correspond to the targets you can build code for if you have
cross compilers installed.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|