1.1 --- a/docs/overview.txt	Sat Jan 23 16:49:56 2010 +0100
     1.2 +++ b/docs/overview.txt	Thu Feb 11 21:28:10 2010 +0100
     1.3 @@ -331,11 +331,20 @@
     1.4  to create a new toolchain. That needs a very little bit of effort on your side
     1.5  but is quite easy. The options to build a toolchain are saved with the
     1.6  toolchain, and you can retrieve this configuration by running:
     1.7 -  ${CT_TARGET}-config
     1.8 +  ${CT_TARGET}-ct-ng.config
     1.9  
    1.10 -This will dump the configuration to stdout, so to rebuild a toolchain with this
    1.11 -configuration, the following is all you need to do:
    1.12 -  ${CT_TARGET}-config >.config
    1.13 +An alternate method is to extract the configuration from a build.log file.
    1.14 +This will be necessary if your toolchain was build with crosstool-NG prior
    1.15 +to 1.4.0, but can be used with build.log files from any version:
    1.16 +  ct-ng extractconfig <build.log >.config
    1.17 +
    1.18 +Or, if your build.log file is compressed (most probably!):
    1.19 +  bzcat build.log.bz2 |ct-ng extractconfig >.config
    1.20 +
    1.21 +The above commands will dump the configuration to stdout, so to rebuild a
    1.22 +toolchain with this configuration, just redirect the output to the
    1.23 +.config file:
    1.24 +  ${CT_TARGET}-ct-ng.config >.config
    1.25    ct-ng oldconfig
    1.26  
    1.27  Then, you can review and change the configuration by running: