scripts/finish: do not try to symlink if sed expr is a no-op

If the sed expression does not transform the
tuple, do not try to create the symlink.
(transplanted from 5d6d3c28a658a65551d4eb5de414fd97b575f314)

scripts/finish: do not try to symlink if sed expr is a no-op

If the sed expression does not transform the
tuple, do not try to create the symlink.

debug/gdb: fix incorrect path

Fix discrepancy between the directory we create,
and the directory into which we install tic.

libc/glibc: fix installed scripts

glibc installs some bash-scripts, but uses the path to the buildtool
bash as interpreter (on the shebang line). This is only a symlink to
the real bash, and thus is not available at runtime.

Fix that by assuming that bash on the target *will* be /bin/bash.

1.7: update version to 1.7.1+hg

Tagging release 1.7.1

1.7: update version to 1.7.1

scripts/wrapper: fix wrong test when checking access to the reall tool

In C, the proper syntax for a bit-wise OR is a single '|', not two.

It worked so far because all was well:
- X_OK == 1
- R_OK||X_OK == 1
- the file we searched for had the x-bit set
-> access( file, R_OK||X_OK ) worked
- inicidentally, the file we searched for also had the r-bit set,
but we were not testing that in fact.
(transplanted from eebcaff6626f09af4f69b7b06f1246a06769d0af)

complibs/gmp: 5.0.0 misses 'EXPERIMENTAL' in the prompt
(transplanted from 95b4a458fd60d3e0911750c2b7c1b6cf36285845)

cc/gcc: fix headers copy for core static
(transplanted from 22ce0c19f06a530d72fd65c89d0777d16c0a97ac)

crosstool-NG.sh: suppress failure message from uname -o

On non-GNU systems (BSD/MacOS) there is no uname -o.
Suppress the failure message on these systems in the
call to set CT_SYS_OS (uname -s actually sets this variable).

yann.morin.1998@anciens.enib.fr: remove 'uname -o' altogether.
(transplanted from acae437fddccd7681c93a3b6c999c0796693d625)

scripts: enhance Makefile for installation

Split the multiple directory copies into autonomous rules.
Fix the autocompletion message.

test-suite: correctly install when not --local

scripts/wrapper: fix wrong test when checking access to the reall tool

In C, the proper syntax for a bit-wise OR is a single '|', not two.

It worked so far because all was well:
- X_OK == 1
- R_OK||X_OK == 1
- the file we searched for had the x-bit set
-> access( file, R_OK||X_OK ) worked
- inicidentally, the file we searched for also had the r-bit set,
but we were not testing that in fact.

cc/gcc: add option do disable PCH

In some cases, using Pre-Compiled Headers breaks the build.
Ass an option to disable building the PCH, as suggested by:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40974

kernel/linux: allow headers from full custom source tree

Accept a local tarball name as the source of the Linux kernel headers,
rather than forcing the user to use either an upstream tarball, or a
local pre-installed headers tree.

kernel/linux: reorder upstream/custom-tree handling

docs/README.freebsd.txt: Short intro for FreeBSD

Provide short README for FreeBSD as a host OS for ct-ng.

docs/README.macos.txt: Provide hints section

Hints for building tool chains.

patches/gdb: Fix canadian building of GDB for powerpc

Adds patch for GDB v6.8, v7.0, v7.0.1 to fix canadian
cross building of GDB for powerpc.

See original patch information here:
http://sources.redhat.com/bugzilla/show_bug.cgi?id=9638

The patch is not required for GDB v7.1 (fixed).

Tested in canadian combination using mingw32 and powerpc toolchains.
Tested to not affect normal cross building of GDB for powerpc target.

Signed-off-by: Martin Lund <mgl@doredevelopment.dk>

complibs/mpc: add latest version

complibs/gmp: 5.0.0 misses 'EXPERIMENTAL' in the prompt

cc/gcc: baremetal requires a two-pass process

Here, we implement a highly ugly hack. I'm not proud of that one...

To build the libstdc++ library, the compiler requires the C library. In
case we build for non-baremetal, this is normally handled by the final
step, later.

But in the case of bare-metal, we never go through the final step (because
it does not work, and it seems complex enough to make it work), so the
baremetal compilers are issued out of the core step.

libc/newlib: build in the 'start files' pass

A few facts:
- building the C library requires a proper core compiler
- core compiler is issued from one of the core passes
- the C library is required to build libstdc++
- newlib is only built for baremetal
- in bare metal, the final compiler is issued from one of the core passes

So we need to build the C library between core pass 1 and core pass 2.
The only place is eithe libc_headers() or libc_start_files(). The most
pertinent seems to be libc_start_files().

So we build newlib from libc_start_files(), and leave libc() empty.

cc/gcc: store core build rules in an array

Using an array makes it easier to add new rules.
Besides, it is easy to expand from build rules to install rules

cc/gcc: implement default for core options

cc/gcc: fix headers copy for core static

complibs/mpfr: update to latest version

libc/uClibc: apply the threading model to the configuration

The threading model shall be be set in the .config file.
Also, offer the choice between 'old/stable' and 'new' linuxthreads.

config: add support for a second part of the generated choices

Some components have configuration options that can depend on
generic options, so they should go below those.

uClibc for example:
- has its own options (wchar...)
- uses the generic options (threads...)
- if linuxthreads chosen, offers two impls

So we need to be able to split the components options in 2,
one part that is above the generic options, and one part that
ends up below the generic options.