summaryrefslogtreecommitdiff
path: root/binary
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2013-02-15 09:08:53 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2013-02-15 09:08:53 +0200
commit663a6689ba14a422cbc714d113b28dad731c44bf (patch)
tree716cc8b0bf3eb6e86826fdf3aa7ee34a51978763 /binary
parent340ee4f40791d16ab778a473788c1a0645b83993 (diff)
Rename file
Diffstat (limited to 'binary')
-rw-r--r--binary/mingw/NOTES (renamed from binary/mingw/new-gcc-version)4
1 files changed, 2 insertions, 2 deletions
diff --git a/binary/mingw/new-gcc-version b/binary/mingw/NOTES
index 6642589..ec2a485 100644
--- a/binary/mingw/new-gcc-version
+++ b/binary/mingw/NOTES
@@ -1,6 +1,6 @@
An overview of steps required to switch to a new GCC version.
-1. Get the MinGW build of this version and get configuration
+1. Get the MinGW build of this GCC version and get configuration
flags (gcc -v). The idea is to build both the cross-compiler
and the native compiler (with linked-in ODB plugin) as close
to the MinGW configuration as possible.
@@ -32,7 +32,7 @@ An overview of steps required to switch to a new GCC version.
3. Adapt older gcc-X.Y.Z-static-plugin.patch (--dry-run) and apply.
This step will probably require careful review of changes in the
plugin code (plugin.h and plugin.c).
- 4. Regegerate configure script in gcc/gcc/. Use the same autoconf
+ 4. Regenerate configure script in gcc/gcc/. Use the same autoconf
version as in the original (see ~/build/autocond-X.Y). For example:
sudo make -C ~/build/autoconf-2.64 install