gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-06 06:14:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated gcc testresults link to be appropriate for gcc 3.4.3

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@4424 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Jeremy Utley 2004-12-19 19:20:39 +00:00
parent 1422130085
commit 86ca6e777e
2 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
chapter01/changelog.xml
View File

@ -44,6 +44,9 @@ of the LFS Book.</para>
</itemizedlist> </itemizedlist>
</listitem> </listitem>
<listitem><para>December 19th, 2004 [jeremy]: Updated GCC-testresults link to
be appropriate for GCC 3.4.3</para></listitem>
<listitem><para>December 19th, 2004 [jeremy]: Fixed shadow instructions so the sed doesn't create a blank file, from Robert Conolly and David Jensen</para></listitem> <listitem><para>December 19th, 2004 [jeremy]: Fixed shadow instructions so the sed doesn't create a blank file, from Robert Conolly and David Jensen</para></listitem>
<listitem><para>December 17th, 2004 [jim]: Upgraded to findutils-4.2.10, <listitem><para>December 17th, 2004 [jim]: Upgraded to findutils-4.2.10,

2
chapter05/gcc-pass2.xml
View File

@ -164,7 +164,7 @@ a summary of the test suite results, run this:</para>
<para>You can compare your results to those posted to the gcc-testresults <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 mailing list for similar configurations to your own. For an example of how
current GCC-&gcc-version; should look on i686-pc-linux-gnu, see current GCC-&gcc-version; should look on i686-pc-linux-gnu, see
<ulink url="http://gcc.gnu.org/ml/gcc-testresults/2004-09/msg00261.html"/>.</para> <ulink url="http://gcc.gnu.org/ml/gcc-testresults/2004-11/msg00569.html"/>.</para>
<para>Having a few unexpected failures often cannot be avoided. The GCC <para>Having a few unexpected failures often cannot be avoided. The GCC
developers are usually aware of these, but haven't yet gotten around to fixing developers are usually aware of these, but haven't yet gotten around to fixing