diff options
| author | Bruce Korb <bkorb@gnu.org> | 2010-03-12 03:49:08 +0000 |
|---|---|---|
| committer | Bruce Korb <bkorb@gnu.org> | 2010-03-12 03:49:08 +0000 |
| commit | c4d7c6fec0370fbc46553152ef8cb313982c488e (patch) | |
| tree | acdfb3fe1a33417356b1040201fb6082b7061986 /fixincludes/README | |
| parent | 314c0fcf8db3cb4507ebde07cf7c1d0018ddbf67 (diff) | |
the fixinc directory is now "fixincludes"
git-svn-id: https://gcc.gnu.org/svn/gcc/trunk@157398 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'fixincludes/README')
| -rw-r--r-- | fixincludes/README | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/fixincludes/README b/fixincludes/README index 5536a34ec98..bd39a0c0469 100644 --- a/fixincludes/README +++ b/fixincludes/README @@ -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. |