diff options
| author | Greg Schafer <greg@linuxfromscratch.org> | 2004-01-22 23:56:16 +0000 |
|---|---|---|
| committer | Greg Schafer <greg@linuxfromscratch.org> | 2004-01-22 23:56:16 +0000 |
| commit | d962702a7c316b338f9497598e1401fed71b28b3 (patch) | |
| tree | 7b56abcb82de81827ebb36aed65d6a468a767c0c /chapter05/gcc-pass2.xml | |
| parent | 5618bb7f5a8a93ec99c98044ee412c87414db204 (diff) | |
Small entity cleanups.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3182 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter05/gcc-pass2.xml')
| -rw-r--r-- | chapter05/gcc-pass2.xml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/chapter05/gcc-pass2.xml b/chapter05/gcc-pass2.xml index 8cd11d026..762ce0d17 100644 --- a/chapter05/gcc-pass2.xml +++ b/chapter05/gcc-pass2.xml @@ -37,7 +37,7 @@ get PTYs working.</para> <para>This time we will build both the C and the C++ compilers, so you'll have to unpack all three GCC tarballs (-core, -g++, and -testsuite) in one and the same working directory. They will all unfold into a single -<filename>gcc-&gcc-version;/</filename> subdirectory.</para> +<filename>&gcc-dir;/</filename> subdirectory.</para> <para>First correct one problem and make an essential adjustment:</para> @@ -77,7 +77,7 @@ variables that override the default optimization flags.</para> <para>Now prepare GCC for compilation:</para> -<screen><userinput>../gcc-&gcc-version;/configure --prefix=/tools \ +<screen><userinput>../&gcc-dir;/configure --prefix=/tools \ --with-local-prefix=/tools \ --enable-clocale=gnu --enable-shared \ --enable-threads=posix --enable-__cxa_atexit \ @@ -128,7 +128,7 @@ through to completion and not stop at the first failure. The GCC test suite is very comprehensive and is almost guaranteed to generate a few failures. To get a summary of the test suite results, run this:</para> -<screen><userinput>../gcc-&gcc-version;/contrib/test_summary | more</userinput></screen> +<screen><userinput>../&gcc-dir;/contrib/test_summary | more</userinput></screen> <para>You can compare your results to those posted to the gcc-testresults mailing list for similar configurations to your own. For an example of how |