|
From: <sv...@va...> - 2005-07-26 22:01:08
|
Author: njn Date: 2005-07-26 23:01:04 +0100 (Tue, 26 Jul 2005) New Revision: 4267 Log: Update for 3.0. Modified: trunk/README Modified: trunk/README =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/README 2005-07-26 10:42:57 UTC (rev 4266) +++ trunk/README 2005-07-26 22:01:04 UTC (rev 4267) @@ -47,8 +47,8 @@ =20 Valgrind is closely tied to details of the CPU, operating system and to a less extent, compiler and basic C libraries. This makes it -difficult to make it portable, so I have chosen at the outset to -concentrate on what I believe to be a widely used platform: x86/Linux. +difficult to make it portable. Nonetheless, it is available for +the following platforms: x86/Linux, AMD64/Linux and PPC32/Linux. =20 Valgrind is licensed under the GNU General Public License, version 2.=20 Read the file COPYING in the source distribution for details. @@ -63,31 +63,32 @@ =20 Building and installing it ~~~~~~~~~~~~~~~~~~~~~~~~~~ -To install from CVS : +To install from the Subversion repository : =20 - 0. Check out the code from CVS, following the instructions at - http://developer.kde.org/source/anoncvs.html. The 'modulename' is - "valgrind". + 0. Check out the code from SVN, following the instructions at + http://valgrind.org/devel/cvs_svn.html. =20 1. cd into the source directory. =20 2. Run ./autogen.sh to setup the environment (you need the standard autoconf tools to do so). =20 + 3. Continue with the following instructions... + To install from a tar.bz2 distribution: =20 - 3. Run ./configure, with some options if you wish. The standard + 4. Run ./configure, with some options if you wish. The standard options are documented in the INSTALL file. The only interesting one is the usual --prefix=3D/where/you/want/it/installed. =20 - 4. Do "make". + 5. Do "make". =20 - 5. Do "make install", possibly as root if the destination permissions + 6. Do "make install", possibly as root if the destination permissions require that. =20 - 6. See if it works. Try "valgrind --tool=3Dmemcheck ls -l". Either - this works, or it bombs out with some complaint. In that case, - please let us know (see www.valgrind.org). + 7. See if it works. Try "valgrind ls -l". Either this works, or it + bombs out with some complaint. In that case, please let us know + (see www.valgrind.org). =20 Important! Do not move the valgrind installation into a place different from that specified by --prefix at build time. This will |