1.1 --- a/docs/overview.txt	Mon Sep 29 20:19:45 2008 +0000
     1.2 +++ b/docs/overview.txt	Wed Oct 01 18:10:40 2008 +0000
     1.3 @@ -283,19 +283,16 @@
     1.4  
     1.5  If you have an existing toolchain, you can re-use the options used to build it
     1.6  to create a new toolchain. That needs a very little bit of effort on your side
     1.7 -but is quite easy. The options to build a toolchain are saved in the build log
     1.8 -file that is saved within the toolchain. crosstool-NG can extract those options
     1.9 -to recreate a new configuration:
    1.10 -  ct-ng extractconfig </path/to/your/build.log >.config
    1.11 +but is quite easy. The options to build a toolchain are saved with the
    1.12 +toolchain, and you can retrieve this configuration by running:
    1.13 +  ${CT_TARGET}-config
    1.14  
    1.15 -will extract those options, prompt you for the new ones, which you can later
    1.16 -edit with menuconfig.
    1.17 +This will dump the configuration to stdout, so to rebuild a toolchain with this
    1.18 +configuration, the following is all you need to do:
    1.19 +  ${CT_TARGET}-config >.config
    1.20  
    1.21 -Of course, if your build log was compressed, you'd have to use something like:
    1.22 -  bzcat /path/to/your/build.log.bz2 |ct-ng extractconfig >.config
    1.23 -
    1.24 -Then, once the configuration has been extracted, run:
    1.25 -  ct-ng oldconfig
    1.26 +Then, you can review and change the configuration by running:
    1.27 +  ct-ng menuconfig
    1.28  
    1.29  ________________________
    1.30                         /