|
|
@@ -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
|
Greg Schafer