cc/gcc: fix recent gcc build

This fix missed conversion of CT_GCC_USE_* to CT_CC_GCC_USE_*.

Signed-off-by: Arnaud Lacombe <lacombar@gmail.com>

complibs/gmp: fix patch against 5.0.1

config: allow libc selection in backend mode

In backend mode, allow the upper-layer build system to force the
C library selection.

config: do not force setting kernel and arch

In backend mode, only enforce the arch and/or kernel selection if the
upper-layer build system effectively forces the selection.

scripts: misc help and auto-complete fixes

- don't list samples in the main help screen
- improve the samples listing in list-samples
- don't document the 'config' action, it's long dead
- document the 'V' environment variable
- improve on START, STOP and PREFIX environment variables
- add PREFIX and V to autocomplete
- advertise auto-complete at install time

kernel/linux: add latest versions: 2.6.33.2 2.6.32.11 2.6.31.13 2.6.27.46

debug/gdb: update version to 7.1

complibs: update versions

GMP : 4.3.2, 5.0.1*
CLooG/PPL: 0.15.8 0.15.9
libelf : 0.8.13

*: patch series added

scripts/addToolsVersion: fix handling libelf

libelf has moved to the companion libraries section,
and is no longer in the tools section.

libc/glibc: add patch to ports-2.9 to fix sjlj from ARM FPU

As discussed there: http://sourceware.org/bugzilla/show_bug.cgi?id=9678#c4

Reported by: Sasha Sirotkin <buildroot@browserseal.com>

config: fix style issues when source-ing files

Always enclose the sourced file between double-quotes (purely for
consistency; enclosing or not are both allowed by the kconfig language).

config: move backend-related options to their own file

config: hide arch and kernel selection when used as a backend

When used as a backend, it is the responsibility of the upper-layer build
system to set the target architecture and kernel.

config: hide options to debug crosstool-NG when a backend

When used as a backend, it does not make sense to debug crosstool-NG,
so hide the option.

config: hide more config options when a backend

Hide the prompts for some behavioral options, for which the upper-layer build
system is responsible for:
- parallel jobs and maximum load
- use pipes
- use custom shell

config: hide paths when used as a backend

When crosstool-NG is used as a backend, it is the responsibility of the
upper-layer build-system to properly set paths, so we just hide the
prompts in this case.

scripts/populate: optimise search loop

Curently, populate will iterate over all ELF (shared objects|executables)
to look for missing NEEDED DSOs, adding to the list at every iterations
of the search loop.

Instead of looking again at previously handled ELF files, recursively
resolve every ELf files.

Also, in case there are a whole lot of files (more than the shell can
accept as arguments list, or creating a command line longer than the
shell can cope with), use a temporary file with the list of files
to search for missing dependencies.

scripts/populate: cleanups and misc fixes

- it's a POSIX compliant shell script: drop bash, use /bin/sh
- fix help text
- use an absolute path for sysroot
- replace "echo" with "printf"
- replace "stat -c '%i'" with "ls -1id"
- replace "pushd / popd" with "cd / cd -"
- remove superfluous break
- bail out if required lib not found, except if forced

scripts/populate: fix handling the forced libraries list-file

If a list-file is used, then each library in the file will be handled
twice (not a real issue, as the second iteration will find the library
already present, just avoid doing the job twice).

scripts/populate: properly locate the sysroot and required tools

This fixes two problems:
- the sysroot might be in a sub-directory (think SYSROOT_DIR_PREFIX)
- it is not needed to have the target tuple to properly detect the sysroot
and the required tools

As a side effect, this script is now no longer dependent on the target
tuple, and in the future, we might be able to share it across many
toolchains (when/if we can install all of them in the same place).

scripts/populate: add -m option, to merge source and dest

Merge the source rootfs into the (pre-existing) destination rootfs,
and populate the result accordingly.

scripts/populate: add option to use an alternate sysroot

Add a new command line option, "-r", which allows the user to specify
an alternate sysroot location to copy libraries from. This is useful
when using the toolchain in combination with a separate root filesystem,
or when working with multiple different root filesystems.

Signed-off-by: Nate Case <ncase@xes-inc.com>

binutils/sstrip: fix when sstrip is disabled

cc/gcc: fix building for powerpc for the 4.4.x series

Reported by: Thomas Petazzoni
http://sourceware.org/ml/crossgcc/2010-03/msg00057.html

Discussions:
http://lists.uclibc.org/pipermail/uclibc/2010-March/043697.html
http://lists.uclibc.org/pipermail/buildroot/2010-March/032790.html
http://ibot.rikers.org/%23uclibc/20100316.html.gz
(search for "copysignl", by kos_tom, blindvt and y_morin)

binutils/sstrip: get rid of ELFkickers

ELFkickers are looong dead and unmaintained, and the sstrip
from buildroot is working fine *and* is maintained.

binutils/sstrip: depends on ELF

No point building sstrip is the target is not ELF.

tools: move sstrip to the binary utilities menu

sstrip is now alone in its 'tools' menu, and we will probably never gain
any other 'tool'. Besides, sstrip is just strip, but a little bit more
agressive, so it deserves going to the 'binary utilities' menu.

debug/gdb: gdb>=7.0 can use MPC, enable for cross-gdb

debug/gdb: add handling of 7_0_or_later

We'll need to differentiate gdb 7.0 or later, from gdb prior to 7.0

debug/gdb: add option to use GMP and MPFR

GMP and MPFR are optional for gdb, so offer a config option.

debug/gdb: can't build a static native gdb if using GMP/MPFR

It is currently impossible to reliably build static GMP/MPFR libs,
so we can't build a static native gdb using them, obviously.

debug/gdb: split menuconfig for easier maintenance

cc/gcc: fix use of companion libraries

complibs: hide prompts

scripts: fix dumping the config for companion libraries for target

Companion libraries can be disable for the host, but still used for
the target (eg. binutils or gdb). Dump the version also in this case.

scripts: fix dumping config

libelf has been moved to being a companion library, now.

config: hide entries when in backend mode

This implies hidding entries for:
- binutils libraries
- dmalloc
- duma
- native gdb
- ltrace
- strace
- sstrip

kconfig: silence a warning about undefined env variable

When using an environment variable to set a config entry,
don'twarn if it is not defined. Update doc accordingly.

config: prepare for build-system backend

When acting as a backend for a build-system, we should not build
any application that runs on the target, that is:
- no native gdb
- no companion libraries
- no binutils libraries
- no debug tools (save for gdbserver)
- ...

Here, we simply prepare the (hidden) config option that will detect
that we are acting as a back-end.

Update doc accordingly.

samples: fix samples

kernel/linux: add latest versions 2.6.32.10 and 2.6.33.1

debug/gdb: fix building the native tic

The native 'tic' will _always_ be run on the build
machine, so no need to handle canadian/native/...

Reported by: Trevor Woerner
http://sourceware.org/ml/crossgcc/2010-03/msg00055.html
(transplanted from 26e89d367ea11660fd3a0bf0bcad8763e4fa21cf)

debug/gdb: fix building the native tic

The native 'tic' will _always_ be run on the build
machine, so no need to handle canadian/native/...

Reported by: Trevor Woerner
http://sourceware.org/ml/crossgcc/2010-03/msg00055.html

scripts: fix the release script to use the C locale

Force use of the C locale to ensure messages are recognised by the script.

1.6: update version to 1.6.1+hg

Tagging release 1.6.1

1.6: update version to 1.6.1

scripts: enhance and fix the release script

samples: update and fix

scripts: fix completion to show samples
(transplanted from bf1f86bdd79fd20126d20795f425f603a5544952)

Merge.

scripts: fix completion to show samples

libc/glibc: add patch to fix binutils version check

Older glibces were not ready to handle binutils >=2.20.
Fix that, and the forseeable future.
(transplanted from 9804e6b75fd31894ee176809f108d41a5b0cbf8b)

libc/glibc: add patch to fix binutils version check

Older glibces were not ready to handle binutils >=2.20.
Fix that, and the forseeable future.

debug/ltrace: properly fix building for powerpc

ltrace uses ppc, whereas crosstool-NG use powerpc.
Fix that by passing the correct value to HOST when calling configure.
(transplanted from 57c71b197ee6ee6f0d551c4f9001f1d06ad2bd8a)

debug/ltrace: fix building on x86

ltrace uses i386 and x86_64, whereas crosstool-NG use x86 for both cases.
Fix that by detecting what bitness we're building for, and pass appropriate
i386 or x86_64 to ltrace's configure.
(transplanted from 55adc838cd68d3692e5eeeb38afb3d619b8b0c1a)

scripts/samples: use the computed '$(sed)', not 'sed'
(transplanted from 26974c3670fdb7f6896b196e08724f91f1a13059)

scripts/showsamples: fix non-POSIX construct
(transplanted from da584d1d6ab803c0a2f7a9b53912426b69a8d322)

scripts: add script to make a release

debug/ltrace: properly fix building for powerpc

ltrace uses ppc, whereas crosstool-NG use powerpc.
Fix that by passing the correct value to HOST when calling configure.

debug/ltrace: fix building on x86

ltrace uses i386 and x86_64, whereas crosstool-NG use x86 for both cases.
Fix that by detecting what bitness we're building for, and pass appropriate
i386 or x86_64 to ltrace's configure.

libc/uClibc: vampirise patches for 0.9.30.2 from builroot

Commit in upstream buildroot:
http://git.buildroot.org/buildroot/commit/?id=43ffd946ad569f3a1d0662de221cd4cb65bdc8e6
Everything on the 0_9_30 branch since the release (0.9.30.3 to be)

kernel/linux: add latest 2.6.32.9 and 2.6.33, remove old 2.6.32.x

complibs: remove headers after build

After the toolchain is built, we do no longer need the headers.
Reported-by: Enrico Weigelt <weigelt@metux.de>

binutils/binutils: add patch to default emulation for mips64

arch: add mips64

This adds initial mips64 config option and build script.

scripts: use more portable sed options

No need for extended regular expressions here.

scripts/samples: use the computed '$(sed)', not 'sed'

samples: fix this MIPS eglibc-based sample

Specify the SVN revision to use for the eglibc snapshot instead of HEAD,
as some patches made their way upstream in the meantime.

comp-libs: make libelf a companion library

When gcc-4.5 is out, it will require libelf. So better make it a
companion library now rather than postponing the ineluctable.

complibs: hide companion libraries for target entry

The companion libraries on the target are required only for internal use by
binutils and gdb. The user should not have to know about this, so hide the
option.

complibs: simplify config file

Although currently the wrapper is directly dependent on
companion libraries, let's still decorelate those two.

complibs: split-up selection for individual libs

binutils/binutils: fix using GMP and MPFR

scripts: fix dumping 'other environment'

Do not sort the environment, it cripples the output.

cc/gcc: simplify the _or_later stuff

scripts/showsamples: fix non-POSIX construct

scripts: add action to extract config from a build.log file

That got removed quite some time ago, but is really usefull to get the
configuration from a build.log file of a failing build.

kernel/linux: add latest 2.6.32.8

config: re-order the log entries inthe menuconfig

scripts: also dump the rest of the environment

scripts: use kernel name (uname -s) when system name (uname -o) is not availabe

'uname -o' is a GNU extension.

scripts/functions: fix date munging when ns are not available

On some systems (eg. *BSD and Darwin), date does not support nanoseconds
(%N) precision. Instead of printing '%N' in this case, it just prints 'N'.
Fix the sed expression to handle this case.

comp-libs/mpfr: fix build on Darwin

libc/eglibc: Add option to optimize for size

Add an option to eglibc to optimize for size using -Os.

Signed-off-by: Richard Strand <richard.strand@icomera.com>

1.6: bump version to 1.6.0+hg

Tagging release 1.6.0

1.6: create maintenance branch, update version to 1.6.0

1.5: close maintenance branch

samples: update samples

Update to the latest set of config options (no config change).
Remove OABI ARM samples.

kernel/linux: add latest versions, remove old dot-releases

scripts: dump the current tuple with show-config

scripts: add action to dump current configuration in humane-readable form

libc/uClibc: remove EXPERIMENTAL for 0.9.30.2

debiug/ltrace: remove EXPERIMENTAL for 0.5.3, remove 0.5.1

debug/strace: remove EXPERIMENTAL for 4.5.19

comp-libs/mpfr: remove EXPERIMENTAL for 2.4.2

comp-libs/mpc: remove EXPERIMENTAL for 0.8.1

arch/sh: remove EXPERIMENTAL

arch/avr32: remove EXPERIMENTAL

libc/newlib: remove EXPERIMENTAL status

Although this have been only slightly tested, no one has really complained,
and it seems to be working fine so far (on AVR32 at least).

cc/gcc: remove 4.3.0

gcc-4.3.0 never got !EXPERIMENTAL, and no one either confirmed nor complained.

cc/gcc: remove EXPERIMENTAL for gcc-4.4

config: rename mirror prompt, update help entry

The mirror is not necessarily on the /LAN/.

config: remove never used/implemented 'ls-lR'

Use of listing (ls-lR) was never implemented, and never used.

1.1: close spurious branch

avr32: close devel branch (merged)

canadian: close devel branch (merged)

bash_array: close devel branch (merged)

gcc-4.4: close devel branch (merged)

newlib: close the obsolete devel branch

newlib has been integrated through the AVR32 stuff, and the newlib branch
has been bit-rotting in the meantime.

1.4: close branch

1.3: close branch

1.2: close branch

1.1: close branch

scripts: Do not create backup files when patching

Some patches may apply with offset and/or fuzz, and would leave .orig files.

libc/glibc: fix retrieving version string

scripts/functions: add git wrapper

Add a git wrapper to retrieve components from their git tree.
Add a git wrapper to create a working copy (in our tarballs dir).
Recognise git trees when searching for local copies.

libc/glibc: get the version string from version.h

We can not rely on the user-provided version string (be it via the
choice, or manually entered), so fallback to reading version.h,
which is both reliable and always present.

scripts/functions: change handling of nochdir

- 'nochdir' must be the first option
- have systematic pushd/popd, even if nochdir

libc/glibc: move some options around

libc/glibc: get rid of the now obsolete CVS stuff

It's now been a while that glibc switched to git from cvs.
Get rid of cvs to download glibc; this will make for a good
cleanup before we add git support! :-)

libc/glibc: add 2.11 and 2.11.1

Merge.

kernel/linux: remove legacy check

Now, we only support building with Linux >=2.6.27.
Get rid of the code that depended on <2.6.18.

binutils/elf2flt: activate elf2flt build

The code has been lying around inactivated for some time.
Let's enable it at last, and see if any one needs it.

arch: add basic m68k support

Signed-off-by: Remy Bohmer <linux@bohmer.net>
[yann.morin.1998@anciens.enib.fr: use defaults for CT_TARGET_ARCH]
Signed-off-by: "Yann E. MORIN <yann.morin.1998@anciens.enib.fr>

global: do not offer the renice option, let's the user handle that

It's broken anyway. Eg.:
- user is already niced at 10
- user configures to renice at 5
- breaks because user is not allowed to 'boost' his/her nice value

Bette let the user handle the renice with:
nice -XX ct-ng 'action'

cc/gcc: add latest 4.4.3, propagate patchset from 4.4.2

Merge.

libc/uClibc: fix the breakage for x86 and Super-H, after the 32/64 merge

scripts/functions: do not compute CT_KERNEL_ARCH, it's obsolete

Since we merged the 32/64-bit archs, and we explicitly used
the Linux kernel arch name, we can get rid of CT_KERNEL_ARCH.

libc/uclibc: use CT_ARCH, in place of CT_KERNEL_ARCH

Since we merged the 32/64-bit archs, and we explicitly used
the Linux kernel arch name, we can get rid of CT_KERNEL_ARCH.

libc/glibc: use CT_ARCH, in place of CT_KERNEL_ARCH

Since we merged the 32/64-bit archs, and we explicitly used
the Linux kernel arch name, we can get rid of CT_KERNEL_ARCH.

kernel/linux: use CT_ARCH, in place of CT_KERNEL_ARCH

Since we merged the 32/64-bit archs, and we explicitly used
the Linux kernel arch name, we can get rid of CT_KERNEL_ARCH.

docs: do not document CT_KERNEL_ARCH, it's going away...

Since we merged the 32/64-bit archs, and we explicitly used
the Linux kernel arch name, we can get rid of CT_KERNEL_ARCH.

debug/gdb: fix the space-damage

debug/gdb: do not expose the ncurses version in the menuconfig

Merge.

scripts/functions: inverse log level ALL and DEBUG

configure: do not require hg when configuring in an hg clone

When configuring in an hg clone, we need hg to compute the version string.
It can happen that users do not have Mercurial (eg. if they got a snapshot
rather that they did a full clone). In this case, we can still run, of
course, so simply fill the version string with a sufficiently explicit
value, that does not require hg. The date is a good candidate.

configure: silently ignore auto-stuff options --build --host and friends

libc/uClibc: rename patches for 0.9.30.2

Port uClibc patches to 0.9.30.2

Some patches from 0.9.30.1 now applied upstream. The reminder have
been only slightly modified to apply cleanly to the new base.

Signed-off-by: Joachim Nilsson <jocke@vmlinux.org>

samples: update armeb-unknown-linux-uclibcgnueabi: use uClibc-0.9.30.2

libc/uClibc: add latest version 0.9.30.2

scripts/addToolVersion: add uClibc hooks

debug/gdb: install ncurses in a temporary place

We only build the static ncurses, to be used to build the native gdb,
and it needs not be available for anyone but us. So install it into
a temporary place, and get rid of it once gdb is built.

debug/gdb: staticaly link to ncurses for the native gdb

Staticaly link the native gdb (the one that runs on the target,
not the cross one that runs on the host) to ncurses.

docs/TODO: remove finished items, update descriptions for remaining items

companion_tools/libtool: Add libtool tool

Add version 2.2.6b of libtool as a companion tool

Signed-off-by: Richard Strand <richard.strand@icomera.com>

companion_tools/automake: Add automake tool

Add version 1.11.1 of automake as a companion tool

Signed-off-by: Richard Strand <richard.strand@icomera.com>

companion_tools/m4: Add m4 tool

Add version 1.4.13 of m4 as a companion tool

Signed-off-by: Richard Strand <richard.strand@icomera.com>

companion_tools/autoconf: add autoconf tool

Initial version of adding autoconf as a companion tool.

Signed-off-by: Richard Strand <richard.strand@icomera.com>
[yann.morin.1998@anciens.enib.fr: use generic overide tools dir]
[yann.morin.1998@anciens.enib.fr: update menu entries]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>

scripts/crosstool-ng: Change overide bin dir

Change the overide bin dir so it can be used by companion tools

Signed-off-by: Richard Strand <richard.strand@icomera.com>
[yann.morin.1998@anciens.enib.fr: more generic overide tools dir]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>

Merge.

libc/newlib: add latest version

scripts/addToolsVersion: add support for newlib

scripts/addToolVersion: cleanups

scripts/addToolVersion: correctly handle the libc categories

scrips/functions: fix downloads using curl

By default curl doesn't folow redirects. This breaks sourceforge downloads.
Add the -L option to curl to fix this.

Curl also downloads the html as a file even when it gets a 404. This breaks
http downloads when using the failback system. Add the -f option to curl to fix
this.

Signed-off-by: Richard Strand <richard.strand@icomera.com>

libc/glibc: correctly handle dual-bitness archs

If the selected ARCH is dual-bitness (eg. supports 32- and 64-bit),
then we need to know the correct place where to fetch some headers.
Currently, this applies only to x86 variants: i386 and x86_64.

scripts/functions: fix extraction

arch/alpha: cleanup Alpha code

config/arch: always select the adequate bitness

Even if the selected ARCH does not support different bitness (or we do
not support building with another bitness), still select the appropriate
bitness.

config/arch: also export bitness as a string

documentation: Remove refs to seemingly native toolchains issue

Remove references to the seemingly native toolchains do not build
issue as it seems to be fixed.

Signed-off-by: Richard Strand <richard.strand@icomera.com>

1.5: update version string to 1.5.3+hg

Tagging release 1.5.3

i1.5: update version string to 1.5.3

libc/uClibc: add patch to fix IP frames on BE targets

Pack netinet structs to be possible to use for creating
IP frames on big-endian targets.

Signed-off-by: Joachim Nilsson <jocke@vmlinux.org>
[yann.morin.1998@anciens.enib.fr: removed getline patch, already in]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
(transplanted from 5c246abe7716271c0ce31d980d92eb9a304995c8)

libc/uClibc: do not mangle ARM {E,O}ABI when ARCH != ARM

(manualy transplanted from 2ad2cbc1f709f48a195746476a71f1244cc67cee)
(transplanted from 2ad2cbc1f709f48a195746476a71f1244cc67cee))

debug/tools: set the ncurses extension to .tar.gz

TRying to download every extension in turn takes ages, so
help the helper by telling what extension to retrieve.
(transplanted from 08b0982e4da9402ad39fde431353ebf0248ea34c)

config: fix generated config files when GREP_OPTIONS set --color=always

grep is used when generating some .in files (in config.gen). If GREP_OPTIONS
contains --color=always, then the generated files will contains some escape
sequences setting the color, and mconf would choke on those escape sequences.

Always set and export an empty GREP_OPTIONS to avoid that.

Issue reported by Kevin Kirkup <kevin dot kirkup at gmail dot com> :
http://sourceware.org/ml/crossgcc/2009-12/msg00026.html
(transplanted from a5020a1facffc046d23d39a71a1b8089ca84beac)

scripts: check for, and warn about an unset CT_PREFIX_DIR

The user shall provide a directory to install the toolchain into.
If he/she does not, this is an error, and shall be detected properly,
rather than relying on failure down the road.

Thanks to "Pedro I. Sanchez" <psanchez@colcan.ca> for pointing out
the issue:
http://sourceware.org/ml/crossgcc/2009-12/msg00011.html
(transplanted from e94f4ffddd1d07b3841160db71694cd19fda6b03)

debug/gdb: Add support for GDB 7.0.1 (minor release)

Signed-off-by: Joachim Nilsson <jocke@vmlinux.org>

config: don't force the vendor part in the tuple

Note however that some configurations (eg. arm-elf) will still
have the vendor part 'unknown' forced in (by config.sub).

samples: update armeb-unknown-linux-uclibcgnueabi

kernel/linux: add support for latest versions

This patch adds support for the latest Linux 2.6.32.3 kernel.

Signed-off-by: Joachim Nilsson <jocke@vmlinux.org>
[yann.morin.1998@anciens.enib.fr: keep only one long-term stable]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>

libc/uClibc: add patch to fix IP frames on BE targets

Pack netinet structs to be possible to use for creating
IP frames on big-endian targets.

Signed-off-by: Joachim Nilsson <jocke@vmlinux.org>
[yann.morin.1998@anciens.enib.fr: removed getline patch, already in]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>

binutils/binultils: import binutils-2.20 patches from OE

This is a set of patches for binutils-2.20 that have been "ported", or rather
shamelessly stolen, from the OpenEmbedded project:

http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/binutils/binutils-2.20

Tried and tested on Arm (big-endian Xscale, and little-endian i.MX27) with GCC 4.4.2

Signed-off-by: Joachim Nilsson <jocke@vmlinux.org>

complibs/mpfr: add upstream patches

cc/gcc: add new patch, fixers building on x86 for target armeb (at least!)

Patch from Ralf Wildenhues:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41818#c5

Testing thanks to Joachim Nilsson:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41818#c7

Merge.

complibs/mpfr: add latest version 2.4.2

Note: the MPFR site happens to be down at the time I wrote
this message, and happens to be down quite often.

Once it's back up'n'runnin', I'll mirror as much as possible
the MPFR tarballs on my site, but in the meantime, you'll
have to handle it by yourself (patience...).

complibs/mpc: add latest version 0.8.1

scripts/addToolsVersion: add support for MPC

cc/gcc: add patch to fix armeb in gcc-4.4

On x86, gcc-4.4.x breaks when building for target armeb.
It is still required to configure with: --disable-shared

Note: if building on an x86_64, there is no need to pass --disable-shared

scripts/addtoolversion: prepare for hooks for tools others than gcc

The upcoming git support will require hooks for glibc as well.

scripts: protect against partially extracted source

In case of failure (eg. user hitting Ctrl-C), avoid extracting over
partially extracted source. Will help once we have git available.

scripts: handle custom or empty extension when extracting

scripts/functions: do not double check if downloads are allowed

Only call the *_get functions if downloads are allowed, so there
is no need to check it again in the retrieval wrappers.

debug/ltrace: fix for a latent bug

debug/ltrace: chop long lines

debug/ltrace: set the ltrace extension to .tar.gz

Trying to download every extension in turn does not work.
The Debian server returns a friendly 404-page that is
saved as the orig.tar.bz2 file. Help the helper by giving
it the extension to retrieve.

debug/ltrace: Add support for ltrace-0.5.3

From this version of ltrace the maintainer has removed support for
GNU Autotools, so the patch sets needed to be reworked.

Included is the latest Debian patch, by the Debian ltrace maintainer
Juan Cespedes <cespedes@debian.org>, the OpenEmbedded patches for cross
compiling, by Khem Raj <raj.khem@gmail.com> and a further set of patches
by Joachim Nilsson <jocke@vmlinux.org> for crosstool-NG.

samples: refine the listing of all samples for canadian samples

For canadian samples, display the sample as:
target-tuple (host: host-tuple)

samples: add an action to print details for all samples

samples: fix displaying samples

samples: add a new samples for the TI DaVinci processors.

Dragan Marinkovic <marinkovic.dragan@gmail.com> wrote:
I finally had the time (and board) to spend some time with
crosstool-NG version 1.5.2 and TMS320DM6446 (DaVinci Digital Media
System-on-Chip,
http://focus.ti.com/docs/prod/folders/print/tms320dm6446.html).

I was able to successfully build and run v2.6.27-davinci1 kernel
(Kevin Hilman's branch) with busybox based initramfs on it. I don't
believe that any later kernel would represent any challenge (it just
happens that I'm currently working with this version). What a thrill
:).

crosstool-NG/toolchain config is attached. It may be useful to someone
using crosstool-NG ...

scripts/functions: make aria2 less verbose when downloading

Merge.

misc: do not use "tar cf - |tar xf -"

Using this: tar cf - -C "/some/place" |tar xf - -C "/some/other/place"
to copy a directory to another place does not properly fail (when it does).

Using this instead: cp -av "/some/place" "/some/other/place"
makes it easy to see why and how it failed.

Impacted:
libc/uClibc
debug/ltrace
tools/sstrip
scripts/populate

Merge.

cc/gcc: update ptachsets for gcc-4.4.{0,1,2}

As reported by Joachim Nilsson <jocke@vmlinux.org>
in: http://sourceware.org/ml/crossgcc/2010-01/msg00005.html

It seems I need to add the 4.3.4/290-index_macro.patch to the GCC 4.4.x
series as well. I immediately trigger the following libstdc++ bug for
4.4.2 with a uClibc .config which has UCLIBC_SUSV3_LEGACY_MACROS set[1].

http://lists.busybox.net/pipermail/uclibc/2006-April/035991.html

libc/uClibc: do not mangle ARM {E,O}ABI when ARCH != ARM

libc/uClibc: beautify the munge function

scripts/functions: fix downloading with aria2

In case the remote file does not exist (and probably for some
other reasons as well), aria2 nonetheless creates an empty file
(or not empty for some other reasons).

The solution is to delete the file whenever aria2 fails.

scripts/functions: fix using Aria2

Latest aria2 no longer recognise the --retry-wait option.

debug/strace: fix strace 4.5.19 to properly build with latest Linux kernels

Here's a couple of patches to get strace 4.5.19 to configure and build
properly with the latest kernel headers. Not pretty, but hopefully
enough while we wait for 4.5.20 to be released.

With the current strace-4.5.19 patches I failed to get the configure
script running even on my host environment. Also, when cross building
the configure script needs to look for the proper system headers to be
able to properly set HAVE_LINUX_NETLINK_H. Otherwise you get:

[EXTRA] Building strace
[ERROR] /home/jocke/x-tools/targets/src/strace-4.5.19/net.c:976:
error: field 'nl' has incomplete type
[ERROR] make[2]: *** [net.o] Error 1
[ERROR] make[1]: *** [all] Error 2

The fix was simple, backport a change set from the git[1] tree and run
autoreconf to update the configure script.

[1] - http://strace.git.sourceforge.net/git/gitweb.cgi?p=strace/strace;a=commit;h=f0df31e71a58c6e79ba77c1a9d84b2f38d44bec7

debug/tools: set the ncurses extension to .tar.gz

TRying to download every extension in turn takes ages, so
help the helper by telling what extension to retrieve.

scripts/functions: add aria2, a powerfull downloader

aria2 is a powerfull downloader that is capable of chunking and
parallel retrieval.

Due to li;itations in crosstool-NG retrieval facilities, it's not possible
to take fully advantage of aria2. It might happen that, in the future,
those limitations get lifted away, so we can take use features such as
parallel downloading from more than one server at the same time. For now,
it should still speed up downloads thanks to parallel downloading of chunks.

scripts/functions: simplify wget vs. curl check

config: fix generated config files when GREP_OPTIONS set --color=always

grep is used when generating some .in files (in config.gen). If GREP_OPTIONS
contains --color=always, then the generated files will contains some escape
sequences setting the color, and mconf would choke on those escape sequences.

Always set and export an empty GREP_OPTIONS to avoid that.

Issue reported by Kevin Kirkup <kevin dot kirkup at gmail dot com> :
http://sourceware.org/ml/crossgcc/2009-12/msg00026.html

linux/kernel: fix version numbers

kernel/linux: add latest versions

kernel/linux: fix versions

scripts: check for, and warn about an unset CT_PREFIX_DIR

The user shall provide a directory to install the toolchain into.
If he/she does not, this is an error, and shall be detected properly,
rather than relying on failure down the road.

Thanks to "Pedro I. Sanchez" <psanchez@colcan.ca> for pointing out
the issue:
http://sourceware.org/ml/crossgcc/2009-12/msg00011.html

scripts: correctly warn when the local tarballs directory does not exist

Warn about a missing local tarball directory, only if it was configured.
Avoid the spurious message:
Directory '${CT_LOCAL_TARBALLS_DIR}' does not exist.
Will not save downloaded tarballs to local storage.

Thanks to "Pedro I. Sanchez" <psanchez@colcan.ca> for pointing out the
issue:
http://sourceware.org/ml/crossgcc/2009-12/msg00011.html

configure: install in a sub-dir of --libdir and --docdir

In case the user specifies the LIBDIR with --libdir , or DOCDIR with
--docdir, install our support files in a sub-dir, so as not to mangle
existing (potentially system) files/dirs.
(transplanted from 991fc21dd3cfda7d6448388b3224821f6937f15e)

configure: install in a sub-dir of --libdir and --docdir

In case the user specifies the LIBDIR with --libdir , or DOCDIR with
--docdir, install our support files in a sub-dir, so as not to mangle
existing (potentially system) files/dirs.

scripts: directly spit-out the date in the WiKi table, misc eye-candy

No need to go through a post-processing just for displaying the date...

scripts: fix Host/Target colums in WiKi table

Generate a better-looking WiKi table by re-arranging
the host and target columns.

scripts: fix WiKi table generation

The number of column in the top-most header was not updated to reflect the
fact that a new column was added to show the host (for canadian crosses).

samples: update the Alpha sample

According to: http://sourceware.org/ml/crossgcc/2009-11/msg00109.html

libc/glibc: update 2.10.1 patchset

According to: http://sourceware.org/ml/crossgcc/2009-11/msg00109.html
update the patchset for correct Alpha build.

patches/glibc: allows glibc2.9 to be compiled with binutils 2.20

the configure script had to be modified to accept as/ld at versions greater
than 2.19
Signed-off-by: Frederic Roussel <fr.frasc@gmail.com>

samples: update the AVR32 sample

scripts: update config.{sub,guess}

1.5: update version string to 1.5.2+hg

Added tag crosstool-ng-1.5.2 for changeset bb01f4294cf2

1.5: update version string to 1.5.2

Fix typos and adjust some documentation.
(transplanted from 19205498184e299fb45a4addebcf7b480f119165)

libc/uClibc: add new patch to fix NULL pointer dereference
(transplanted from 3d8f6d826f21342b6172813384f3e5e1f09e8a71)

scripts: fix updating config.{sub,guess}
(transplanted from 7f52e1cca71eecc6a46ad1905afea42a5c8f0a68)

libc/uClibc: fix building on system with recent glibc

While trying to build a toolchain with ct-ng 1.5.0,
arm-unknown-linux-uclibcgnueabi target,
I get the following error:

[INFO ] Installing C library headers
[EXTRA] Copying sources to build dir
[EXTRA] Applying configuration
[EXTRA] Building headers
[EXTRA] Installing headers
[ERROR] extra/scripts/unifdef.c:209: error: conflicting types for 'getline'
[ERROR] make[2]: *** [extra/scripts/unifdef] Error 1
[ERROR] Build failed in step 'Installing C library headers'

The following patch solves the problem.
(It's a backport of this uClibc commit:
http://git.uclibc.org/uClibc/commit/?id=49e81cada73616864b9b31df0aeb6961c30f5a6e
)

[--SNIP from another mail--]
AFAIK this is a problem since glibc 2.10.
(transplanted from 1ba79f2126df8bd89120899a58f2d0bcc2e9c771)

libc/newlib: fix host/target confusion

newlib handles the build/host/target a bit differently as one would expect:
build : not used
host : the nachine that builds newlib
target : the machine on which newlib will run
(transplanted from 3ccb1f76576fc7b730c57a0d1e183bce20cc47c0)

Fix typos and adjust some documentation.

Adding kernel 2.6.31.6 and 2.6.27.39

libc/glibc: configure libc headers with support for 128-bit long double

At the headers install pass, there's no compiler to test for the size
of long double. Help it: we know that the compiler does support 128-bit
long double, in the IBM extended precision.

Kindly pointed out, and explained, by Mike FRYSINGER:
http://sourceware.org/ml/crossgcc/2009-11/msg00040.html
http://sourceware.org/ml/crossgcc/2009-11/msg00057.html