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.

docs: update credtis, point to the repository log

The docs/CREDITS file dates back to the SVN repository.
Now that we use Mercurial, the repository stores appropriate
authorship for each commit. Say so in the CREDITS.

kernel/linux: update to latest versions

kconfig/lxdialog: more portable and use ncurses from macports on MacOS

check-lxdialog.sh now correctly tests for ncurses and is a bit more portable.
On Darwin it uses the ncurses from macports.

cc/gcc: Make usage of --enable-target-optspace configurable

Optionally configure to compile gcc-internal libs with -Os.

yann.morin.1998@anciens.enib.fr:
Rename the config options, it is in the GCC /namespace/.

docs: Provide new Readme for MacOS

Short README for usage of ct-ng under MacOS.
Remove obsolete MacOS-X.txt

yann.morin.1998@anciens.enib.fr:
Make it 80-columns clean, plus a few fixes

scripts/build/internals.sh: compile wrapper with portable options.

static linking is not possible on MacOS, and unnessecary on other systems.
The old optimization and warning flags crash the gcc on MacOS
and (imho) are a bit overdone for this software.

configure: add path to libtool to pathlist

forgot var=libtool

debug/ltrace: fix LDFLAGS for libsupc++ and libiberty

The configure script correctly detects libsupc++ and libiberty, but in
the linker stage it tries to link in both libraries without taking care
of the test result.

Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
[yann.morin.1998@anciens.enib.fr: rework patch depth to be -p1]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>

libc/glibc: fix as/ld checks against recent binutils

Backported from:
http://sourceware.org/ml/libc-alpha/2009-09/msg00024.html

Thanks to Khem RAJ for pointing to this fix:
http://sourceware.org/ml/crossgcc/2010-05/msg00033.html

test-suite: apply cleanup pass

Remove all non-modifiable items (target tuple, gcc version, toolchain path...)
Makefile syntax ( use $(...) instead of ${...} )
Update doc
Space-damage cleanups

test-suite: Added new test suite feature (experimental)

This patch adds support for installing the gcc test suite. A helper
Makefile is provided for building and running the gcc tests.

The default configuration runs all gcc tests and requires automatic
ssh/scp login access to a networked target board. See README for
more details.

Note: Current feature is tested with the powerpc-unknown-linux-gnu
sample but it should work with others as well.

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

scripts/wrapper.c: Under MacOS set DYLD_LIBRARY_PATH

Depending on (predefined) macro __APPLE__, use DYLD_LIBRARY_PATH
instead of LD_LIBRARY_PATH.

docs/overview.txt: Provide short mercurial HOWTO

The usage of hg mq is imho not very well documented.
Give a short intro for the most important use cases
for contributions to ct-ng.

yann.morin.1998@anciens.enib.fr:
Slightly rewrote the explanations for the introductory message.

ct-ng: Add ability to configure and use some GNU tools

Make the paths to libtool, objcopy, objdump, readelf, patch configurable.

scripts/build/internals.sh: Always use binary wrapper under BSD/MacOS

The shell wrapper script uses a nonportable call to readlink.
Thus, always use the binary wrapper under BSD/MacOS.

yann.morin.1998@anciens.enib.fr:
Use 'case' instead of 'if'.

scripts/wrapper.in: Add a comment about readlink not being portable.

Documented that the call to readlink will not work on BSD systems.

configure: make call to readlink portable to non-GNU (BSD) systems

The argument '-e' for readlink is a GNU extension.
In setting the variable 'where' the argument '-e' is not necessary, thus eliminated.

scripts/crosstool-NG.sh.in: On MacOS/BSD use the output of CT_DoConfigGuess for CT_BUILD.

On 64bit MacOS `gcc -dumpmachine` gives i686 for the host machine.
This conflicts with the expectations of some following configure scripts
that a 64bit x86 is given as x86_64; i686 is understood as a 32 bit machine.
config.guess sets the host machine in CT_BUILD correctly.

yann.morin.1998@anciens.enib.fr:
As suggested by Khem RAJ on the ML, always use config.guess.

configure: Do not require stat to be of GNU coreutils

calls to stat have been made portable, thus it is not necessary
that the GNU version is present on the user's system.

scripts/functions: Use stat correctly on non-GNU (BSD/Darwin) systems.

Call to get the directory mode depending on $CT_SYS_OS

yann.morin.1998@anciens.enib.fr:
CT_SYS_OS has changed on Linuxsystem, it only gets the kernel name "Linux",
and not the system name, 'GNU/'.

build/internals.sh: Replace nonportable call to stat

The call to stat to find out if a file is a symlink works only on GNU systems,
and the replacing portable call to readlink is also shorter and more concise code.

yann.morin.1998@anciens.enib.fr:
Apply simpler test, after discussion with author and Arnaud LACOMBE on the ML.

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.

cc/gcc: add latest version

Add 4.4.4 and forward-port patchset from 4.4.3

kernel/linux: update versions list

Merge.

Revert changeset e7f7220b5ba2

Arnaud LACOMBE rightly pointed out that this was done on the wrong branch.

Revert changeset d341be24dc68

Arnaud LACOMBE rightly pointed out that this was done on the wrong branch.

cc/gcc: add latest version

Add 4.4.4 and forward-port patchset from 4.4.3

kernel/linux: update versions list

1.7: update version to 1.7.0+hg

Tagging release 1.7.0

1.7: create maintenance branch, update version to 1.7.0

scripts/mk-release: pretty-up the per-author stats

Reverse sort first by number of changesets, then sort alphabetically
on the author's names.

docs: update the known issues

samples: update