Only create the state dir if asked for a restartable build:
- introduce the config dir, where components can store their config files
- move the munged uClibc config file to the config dir
- now, the state dir really is an indication that a build can be restarted

Thanks to Groleo Marius <groleo@gmail.com> for spotting the inconsistency
of the state dir usage, and suggesting this change.

/trunk/scripts/build/libc/uClibc.sh | 6 3 3 0 +++---
/trunk/scripts/crosstool-NG.sh.in | 9 7 2 0 +++++++--
/trunk/scripts/functions | 15 12 3 0 ++++++++++++---
3 files changed, 22 insertions(+), 8 deletions(-)

Detect and abort on partially patched component.

/trunk/scripts/functions | 18 15 3 0 +++++++++++++++---
1 file changed, 15 insertions(+), 3 deletions(-)

Refuse to build/install on file systems that are *not* case-sensitive.

/trunk/scripts/crosstool-NG.sh.in | 9 9 0 0 +++++++++
1 file changed, 9 insertions(+)

Merge r1432:1437 from /branches/newlib into /trunk :
- under bare-metal, the user is responsible for providing a gdbserver stub (r1433)
- install a CT_TARGET-cc -> CT_TARGET-gcc symlink for the core gcc (r1434)
- allow broader dependency in generated config files (r1435, r1436)
- prepare C library menuconfig for using a C library under bare-metal (r1437)

/trunk/scripts/build/cc/gcc.sh | 4 4 0 0 ++++
/trunk/config/debug/gdb.in | 5 5 0 0 +++++
/trunk/config/libc/glibc.in | 1 1 0 0 +
/trunk/config/libc/uClibc.in | 1 1 0 0 +
/trunk/config/libc/eglibc.in | 2 1 1 0 +-
/trunk/config/config.mk | 20 8 12 0 ++++++++------------
/trunk/config/arch/sh.in | 2 1 1 0 +-
/trunk/config/arch/ia64.in | 2 1 1 0 +-
/trunk/config/arch/powerpc64.in | 2 1 1 0 +-
/trunk/config/libc.in | 4 0 4 0 ----
10 files changed, 23 insertions(+), 20 deletions(-)

Add support for building toolchains with gcc-4.4 snapshots.
Initial patch by Dmitry PLOTNIKOV: http://sourceware.org/ml/crossgcc/2009-03/msg00053.html
It [the toolchain] uses current ct-ng (nightly snapshot 20090324, latest
release 1.3.2 work also), glibc 2.9 (from CVS), binutils 2.19 and latest
snapshot of GCC 4.4.0 (as of March 20, 2009).

We have successfully built linux kernel 2.6.29 and a lot of other stuff
with this toolchain.

Here's the patch that adds GCC 4.4.0 to the ct-ng menu and enables it to
download a 4.4.0 snapshot from ftp.

Patch was adpated by me, mostly to better fit the configuration layout.

/trunk/scripts/build/cc/gcc.sh | 34 22 12 0 ++++++++++++++++++++++------------
/trunk/config/cc/gcc.in | 35 30 5 0 ++++++++++++++++++++++++++++++-----
2 files changed, 52 insertions(+), 17 deletions(-)

Finally make ncurses-5.7 corctly build:
- find the executables extension (needed under some OS, like Winblows)
- build tic in //
- simplify the make and install command lines

/trunk/scripts/build/debug/300-gdb.sh | 10 7 3 0 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)

Log the save/restore messages at a level that is always visible.

/trunk/scripts/functions | 7 5 2 0 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)

Final touch to the ncurses build step:
- use build tools to build tic, instead of native ones.

/trunk/scripts/build/debug/300-gdb.sh | 9 6 3 0 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)

xlcwu <xlcwu.taiwan@gmail.com> wrote:
Seems ncurses 5.7 need build host stage for tic step; if use host tic
(ubuntu) the build process hang in the below step.
So I guess need to build ncurses host stage to build new tic

and provided a patch to that efect.

And in fact, we do need "tic" to run on the _build_ system to properly
generate the terminfo database.

Note: this is fully functional, but still requires a litle bit of
tweaking so that ${CT_BUILD}-gcc gets used instead of plain gcc.
But that's a minor problem for now...

/trunk/scripts/build/debug/300-gdb.sh | 35 33 2 0 +++++++++++++++++++++++++++++++++--
/trunk/scripts/build/internals.sh | 1 1 0 0 +
2 files changed, 34 insertions(+), 2 deletions(-)

Fix the menuconfig comment stating that native gdb needs a native ncurses
library, rather than saying it needs the ncurses library on the target.

/trunk/config/debug/gdb.in | 2 1 1 0 +-
1 file changed, 1 insertion(+), 1 deletion(-)