X-Git-Url: http://git.sourceforge.jp/view?a=blobdiff_plain;f=fixincludes%2FREADME;h=07a3964a26aaaf082c7bb996d32d93f348bd335c;hb=fa988518602d252c9d11553037b6c0f4eefeeaa0;hp=5536a34ec9855720092532c5f8daa7338be47498;hpb=b795c8d1f5cc95979bc8871b21fcb2896900d7fa;p=pf3gnuchains%2Fgcc-fork.git

diff --git a/fixincludes/README b/fixincludes/README
index 5536a34ec98..07a3964a26a 100644
--- a/fixincludes/README
+++ b/fixincludes/README
@@ -6,7 +6,7 @@ See also:  http://autogen.SourceForge.net/fixinc.html
 
 The set of fixes required was distilled down to just the data required
 to specify what needed to happen for each fix.  Those data were edited
-into a file named gcc/fixinc/inclhack.def.  A program called AutoGen
+into a file named fixincludes/inclhack.def.  A program called AutoGen
 (http://autogen.SourceForge.net) uses these definitions to instantiate
 several different templates that then produces code for a fixinclude
 program (fixincl.x) and a shell script to test its functioning.  On
@@ -45,7 +45,7 @@ To make your fix, you will need to do several things:
     "test_text" entry(ies) that validate your fix.  This will
     help ensure that future fixes won't negate your work.
 
-5.  Go into the fixinc build directory and type, "make check".
+5.  Go into the fixincludes build directory and type, "make check".
     You are guaranteed to have issues printed out as a result.
     Look at the diffs produced.  Make sure you have not clobbered
     the proper functioning of a different fix.  Make sure your
@@ -319,7 +319,7 @@ EXAMPLES OF FIXES:
 
     I would really recommend, however:
 
-        cd ${top_builddir}/gcc/fixinc
+        cd ${top_builddir}/fixincludes
         make check
 
     To do this, you *must* have autogen installed on your system.