|
From: Nicholas N. <nj...@cs...> - 2005-08-28 15:45:59
|
On Sun, 28 Aug 2005, Tom Hughes wrote: > That is my plan, yes. It's a bit more complicated than that because > if it is a script you have to parse the #! line to get the interpreter > and then probe the ELF header of the interpreter. Yes. This trivial wrapper is quickly looking like the old stage1.c :) > 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. N |