2012-10-22fix eglibc-2.16 manual build
Johannes Stezenbach <js@sig21.net> [Mon, 22 Oct 2012 03:32:28 +0000] rev 3087
fix eglibc-2.16 manual build

Signed-off-by: Johannes Stezenbach <js@sig21.net>
Message-Id: <20121022133228.GA16536@sig21.net>
Patchwork-Id: 193156

2012-10-22kernel/linux: add altest versions
"Yann E. MORIN" <yann.morin.1998@free.fr> [Mon, 22 Oct 2012 22:40:01 +0200] rev 3086
kernel/linux: add altest versions

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

2012-10-21scripts/functions: return a proper error code in CT_DoExecLog
"Yann E. MORIN" <yann.morin.1998@free.fr> [Sun, 21 Oct 2012 22:27:17 +0200] rev 3085
scripts/functions: return a proper error code in CT_DoExecLog

Since we added the debug-shell feature, CT_DoExecLog no longer
returns the error code of the command, but always return 0.

This breaks the download mechanism, which relies on CT_DoExecLog
to fail _on_purpose_ to detect that the ressource was not found
at the specified URL.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

2012-10-17scripts/functions: properly catch failure in CT_Test* helpers
"Yann E. MORIN" <yann.morin.1998@free.fr> [Wed, 17 Oct 2012 22:01:25 +0200] rev 3084
scripts/functions: properly catch failure in CT_Test* helpers

So we get caught by the trap-handler and
have a chance to run the debug-shell.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Johannes Stezenbach <js@sig21.net>

2012-10-06scripts: add option to start an interactive debug shell
"Yann E. MORIN" <yann.morin.1998@free.fr> [Sat, 06 Oct 2012 23:48:07 +0200] rev 3083
scripts: add option to start an interactive debug shell

Add an option that, when a command fails:
- starts an interactive shell with the failed command's environment
- attempts re-execution of the failed command, continues, or aborts
at user's whim.

Before starting the debug-shell, the backtrace is printed.
When exiting for an abort, the standard error message is printed.

Based on an idea and a patch from: Johannes Stezenbach <js@sig21.net>
http://sourceware.org/ml/crossgcc/2012-09/msg00144.html

Signed-off-by: Johannes Stezenbach <js@sig21.net>
[yann.morin.1998@free.fr: integrate in the fault handler]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Acked-by: Johannes Stezenbach <js@sig21.net>
Patchwork-Id: 191571
Patchwork-Id: 191668

2012-10-14scripts: move backtrace marker to CT_WORK_DIR
Johannes Stezenbach <js@sig21.net> [Sun, 14 Oct 2012 23:46:15 +0000] rev 3082
scripts: move backtrace marker to CT_WORK_DIR

Avoid error when commands in scripts/crosstool-NG.sh fail
before CT_BUILD_DIR is set.

So we need to remove the backtrace marker of a potential previous
build. Previously, it was implicitly removed because we did remove
the directory it was in, which is no longer the case.

Signed-off-by: Johannes Stezenbach <js@sig21.net>
[yann.morin.1998@free.fr: remove backtrace marker on start of build]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Message-Id: <20121015094615.GA18673@sig21.net>
Patchwork-Id: 191498

2012-10-17scripts: fix default work-dir name
"Yann E. MORIN" <yann.morin.1998@free.fr> [Wed, 17 Oct 2012 21:52:59 +0200] rev 3081
scripts: fix default work-dir name

It's been a long time the default work-dir changed its name
from 'target' to '.build'.

Change the left-over.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

2012-10-17kernel/linux: fix missing 'then'
"Yann E. MORIN" <yann.morin.1998@free.fr> [Wed, 17 Oct 2012 21:21:44 +0200] rev 3080
kernel/linux: fix missing 'then'

Reported-by: David Holsgrove <david.holsgrove@xilinx.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

2012-10-16kernel/linux: fix using custom location
"Yann E. MORIN" <yann.morin.1998@free.fr> [Tue, 16 Oct 2012 20:57:44 +0200] rev 3079
kernel/linux: fix using custom location

Currently, extract and patch are skipped as thus:
- using a custom directory of pre-installed headers
- a correctly named directory already exists

Otherwise, extract and patch are done.

The current second condition is wrong, because it allows the following
sequence to happen:
- a non-custom kernel is used
- a previous build only partially extracted the non-custom sources
- that p[revious build broke during extraction (eg. incomplete tarball...)
- a subsequent build will find a properly named directory, and will
thus skip extract and patch, which is wrong

Fix that by following the conditions in this table:

Type | Extract | Patch
----------------------+---------+-------
Pre-installed headers | N | N
custom directory | N | N
custom tarball | Y | N
mainstream tarball | Y | Y

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: David Holsgrove <david.holsgrove@xilinx.com>

2012-10-15scripts: update config.sub
David Holsgrove <david.holsgrove@xilinx.com> [Mon, 15 Oct 2012 16:59:11 +1000] rev 3078
scripts: update config.sub

Latest from upstream config-patches repo. (No change to config.guess)

Signed-off-by: "David Holsgrove" <david.holsgrove@xilinx.com>
Message-Id: <f15b7c69c142e935391e.1350284600@localhost.localdomain>
Patchwork-Id: 191476