Implement a restart facility.

If you select to debug ct-ng, then you have two new options:
 - DEBUG_CT_PAUSE_STEPS : pause between every steps,
 - DEBUG_CT_SAVE_STEPS  : save state between every steps.
To restart a saved state, just set the RESTART make variable when calling make:
  - make RESTART=<step_name>

1 files changed, 69 insertions, 0 deletions

diff --git a/config/global.in b/config/global.in
index 5d91847..0523a0c 100644
--- a/config/global.in
+++ b/config/global.in
@@ -1,7 +1,16 @@
 # Overall toolchain configuration: paths, jobs, etc...
 
+# Ah, this option is here to break the dependency tracking, and allow
+# dependent option to line-up with the options they depend on ,rather
+# than being indented
+config FOOBAR
+    bool
+    default n
+
 menu "Paths and misc options"
 
+comment "Crosstool behavior"
+
 config EXPERIMENTAL
     bool
     prompt "Try features marked as EXPERIMENTAL"
@@ -26,6 +35,64 @@ config OBSOLETE
       Such obsolete features are the use of old kernel headers, old
       gcc versions, etc...
 
+config DEBUG_CT
+    bool
+    prompt "Debug crosstool-NG"
+    default n
+    help
+      Say 'y' here to get some debugging options
+
+if DEBUG_CT
+
+config DEBUG_CT_PAUSE_STEPS
+    bool
+    prompt "Pause between every steps"
+    default n
+    help
+      Say 'y' if you intend to attend the build, and want to investigate
+      the result of each steps before running the next one.
+
+config DEBUG_CT_SAVE_STEPS
+    bool
+    prompt "Save intermediate steps"
+    default n
+    help
+      If you say 'y' here, then you will be able to restart crosstool-NG at
+      any step by typing:
+          make RESTART=<step_nane>
+      
+      where step_name is one of:
+        - kernel_hdr
+        - binutils
+        - libc_hdr
+        - cc_core
+        - libfloat
+        - libc
+        - cc
+        - libc_fin
+        - debug
+      
+      It is not currently possible to rstart at any of the debug facility.
+      They are treated a s a whole.
+
+config DEBUG_CT_SAVE_STEPS_GZIP
+    bool
+    prompt "gzip saved states"
+    default y
+    depends on DEBUG_CT_SAVE_STEPS
+    help
+      If you are tight on space, then you can ask to gzip the saved states
+      tarballs. On the other hand, this takes some longer time...
+      
+      To lose as less time as possible, the gzip process is done with a low
+      compression ratio (-3), which gives roughly 70% gain in size. Going
+      further doesn't gain much, and takes far more time (believe me, I've
+      got figures here! :-) ).
+
+endif
+
+comment "Build behavior"
+
 config PARALLEL_JOBS
     int
     prompt "Number of parallel jobs"
@@ -157,6 +224,8 @@ config ONLY_DOWNLOAD
       
       Usefull to pre-retrieve the tarballs before going off-line.
 
+config FOOBAR
+
 comment "Extracting"
     depends on ! ONLY_DOWNLOAD