|
From: Robert W. <rj...@du...> - 2005-06-15 17:59:52
|
I was wondering what the plan for supporting shipping of Valgrind 3 on
AMD64 machines was? A particular build of Valgrind supports either 32-
bit or 64-bit executables, but not both. AMD64 machines support both,
which implies perhaps shipping a valgrind.x86_64 and valgrind.i386 rpm.
To avoid name clashes, something needs to be done with the stuff that's
not in /usr/{lib,lib64}.
Here's my thoughts, in random order. I've haven't looked at how
feasible any of these are:
* AMD64 builds build both types. stage1 is a single execuable
that can load a particular stage2 from /usr/lib or /usr/lib64
based on the ELF-type of the program under test.
* Same as above, but with separate builds.
* Either of the above, but make valgrind a script that runs the
real stage1.
* Put the onus on the user to do the right thing - ship a valgrind
and valgrind32, say, like I've seen done with strace on some
distros. Craft each build to avoid name clashes.
As for random parts of the build:
* Make /usr/include/valgrind arch-specific (for
example, /usr/include/valgrind-i386) like the kernel does
for /usr/include/asm and friends.
* What to do with /usr/share/doc/valgrind?
Any thoughts?
Regards,
Robert.
--=20
Robert Walsh
Amalgamated Durables, Inc. - "We don't make the things you buy."
Email: rj...@du...
|