From: Russell E. O. <rowen@u.washington.edu> - 2009-05-15 18:48:21
|
In article <200...@ac...>, Julian Seward <js...@ac...> wrote: > On Thursday 14 May 2009, Russell E. Owen wrote: > > I'm trying to install Valgrid 3.4.1 on a shared disk in such a way that > > all of our users can use it, though we have a mix of various flavors of > > linux box (x86 64-bit, 32-bit and AMD64). > > > > I assume this is the relevant section of the documentation, but I cannot > > make heads or tails out of it: > > > > --- begin quote --- > > > > Compiling For Multiple Architectures > > ==================================== > > > > You can compile the package for more than one kind of computer at the > > same time, by placing the object files for each architecture in their > > own directory. To do this, you must use a version of `make' that > > supports the `VPATH' variable, such as GNU `make'. `cd' to the > > directory where you want the object files and executables to go and run > > the `configure' script. `configure' automatically checks for the > > source code in the directory that `configure' is in and in `..'. > > Urr, that's standard GNU boilerplate guff. I don't know if it applies > to us or not. Highly confusing boilerplate (though tom fogal's reply helped clarify it). Fortunately I appears that I don't need it... > Anyway (unless I misunderstand something) this should work right out > of the box, no monkey business, no nothing. > > ./configure --prefix=/place/i/want/it/installed > make > make install > > Then /place/i/want/it/installed/bin/valgrind should be able to handle > both 32-bit and 64-bit executables. One thing to look out for, though, > is at the end of the ./configure run: you need to see > > Primary build target: AMD64_LINUX > Secondary build target: X86_LINUX > > If you don't get that, then you will indeed be out of luck (w.r.t. a > dual-arch build.) I did get that (or something very similar) and it seems to have built correctly. Thank you very much! -- Russell |