Revisit the extract-config way of working: ct-ng is the sole entry point to crosstool-NG, and ct-ng.extrac-config no longer exists. You now have to call "ct-ng extractconfig </path/to/your/build.log" instead.

1 files changed, 23 insertions, 0 deletions

diff --git a/tools/extract-config.sh b/tools/extract-config.sh
new file mode 100755
index 0000000..b5c77c6
--- /dev/null
+++ b/tools/extract-config.sh
@@ -0,0 +1,23 @@
+#!/bin/sh
+
+# This scripts extracts a crosstool-NG configuration from the log file
+# of a toolchain build with crosstool-NG.
+
+# Usage: cat <logfile> |$0
+
+awk '
+BEGIN {
+  dump = 0;
+}
+
+$0~/Dumping crosstool-NG configuration: done in.+s$/ {
+  dump = 0;
+}
+
+dump == 1 { $1 = "" }
+dump == 1
+
+$0~/Dumping crosstool-NG configuration$/ {
+  dump = 1;
+}
+' |cut -d ' ' -f 2-