1.1 --- a/docs/overview.txt	Fri Jul 13 14:25:06 2007 +0000
     1.2 +++ b/docs/overview.txt	Tue Jul 17 21:44:33 2007 +0000
     1.3 @@ -165,6 +165,22 @@
     1.4    brave enough, you can try and debug them. They are hidden behind CT_BROKEN,
     1.5    which itself is hiddent behind EXPERIMENTAL.
     1.6  
     1.7 +Re-building an existing toolchain |
     1.8 +----------------------------------+
     1.9 +
    1.10 +If you have an existing toolchain, you can re-use the options used to build it
    1.11 +to create a new toolchain. That needs a very little bit of effort on your side
    1.12 +but is quite easy. The options to build a toolchain are saved in the build log
    1.13 +file that is saved within the toolchain. crosstool-NG can extract those options
    1.14 +to recreate a new configuration:
    1.15 +  ct-ng extractconfig </path/to/your/build.log
    1.16 +
    1.17 +will extract those options, prompt you for the new ones, which you can later
    1.18 +edit with menuconfig.
    1.19 +
    1.20 +Of course, if your build log was compressed, you'd have to use something like:
    1.21 +  bzcat /path/to/your/build.log.bz2 |ct-ng extractconfig
    1.22 +
    1.23  ________________________
    1.24                         /
    1.25  Running crosstool-NG  /