From: tom f. <tf...@al...> - 2009-05-14 18:13:59
|
"Russell E. Owen" <rowen@u.washington.edu> writes: > 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). [snip] > `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 `..'. > > --- end quote --- > > I have my source code unpacked in a dir on my local disk. Normally I'd > do this in the root of the unpacked source: > ./configure --prefix=desired-location-on-shared-disk > but apparently that's not sufficient to get a build that supports > multiple platforms. So what to do instead? The instructions say: The documentation is simply telling you to do an out of source build. I'm not sure if you can use the same prefix for each different architecture; I'd say try it and test. I wouldn't say it's a huge deal to have the user choose their architecture though. In general, on Linux, you can't mix multiple archs to create anything like OS X's universal binary. So the exact same executable file cannot be executable on both ppc and x86_64, for example. Anyway, the process you want is something like this: cd /to/some/valgrind/directory wget http://.../valgrind-3.4.1.tar.bz2 tar jxvf valgrind-3.4.1.tar.bz2 mkdir x86_64-build mkdir x86-build mkdir ppc-build # or whatever, continue as necessary cd x86_64-build ../valgrind-3.4.1/configure --whatever # options appropriate for x86_64 make # likely `make install' too. cd ../x86-build ../valgrind-3.4.1/configure --whatever # options appropriate for x86 make and so on and so forth, once for each arch. "--whatever" might include "--prefix=/shared/disk/valgrind" in each case; but like I mentioned initially it might need to be "--prefix=/shared/disk/valgrind/x86_64", "--prefix=/shared/disk/valgrind/x86", etc. HTH, -tom |