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

libc/uClibc: add new patch to fix NULL pointer dereference

libc/uClibc: add wchar support

arch: cleanup the 32- and 64-bit selection

arch/ia64: update to the new 64-bit infrastructure

arch/s390: commonalise the 32- and 64-bit s390 arch

arch/x86: commonalise the 32- and 64-bit x86 arch

arch/ppc: commonalise the 32- and 64-bit PowerPC arch

arch: add hidden config knobs for 32- and 64-bit support and select

Add new hidden config knobs that architectures can select to
say whether they support 32- or 64-bit variants, and which
they default to.

Merge.

arch/s390: cleanups

Don't select unneeded config knobs. Don't select non-existing config knobs.
Use the "no patch" config knob, instead of pointing to an non-exiting local
patch dir. Simplify the tuple-related scripts. Update the samples.

config/global: enable not using patches at all

It can be needed to build a toolchain with no patch at all.

arch: add s390 and s390x architectures and samples

Merge.

libc/glibc: allow more than one line in configparms

samples: update the armeb-unknown-linux-gnueabi sample to use glibc-2.10.1

libc/glibc: add 2.10.1

Woo... It seems the glibc guys finally decided that tarballs
were not deprecated, in fact.

The patchset was vampirised from Gentoo (kudos, guys!), and
applies to glibc+ports, so that's why it's been added as a
patchset against ports, not against glibc.

scripts: add a new helper script to easily rediff a patchset

scripts: be POSIXly correct in helper scripts

Fix helper scripts to be POSIXly correct: don't expect '.' (the dot
builtin) to search CWD if it is not in $PATH.

scripts: output renumbered patches in a new directory

When renumbering patches, the original patches get removed and replaced
with the new ones. This can be annoying to loose the original patches.
Fix this by putting the new patchs in a directory of their own.

patches/binutils/2.20: make patches appliable

Fix filenames in patch files for binutils-2.20.
Some patch files were only usable with patch argument '-p0'.
Fix the diff context to match 2.20 release.

Signed-off-by: Frederic Roussel <fr.frasc@gmail.com>

scripts: some eye-candy

scripts: update config.{sub,guess}

scripts: fix updating config.{sub,guess}

Merge.

samples: update all samples to the new set of options

No version change is made.

config: mark now old versions as being OBSOLETE

These versions are kept for the upcoming release, but they
will be removed from the next release if they are not used.

config/binutils: add latest version 2.20

Also add patchset vampirised from Gentoo.

debug/strace: add latest version, unmarkprevious EXPERIMENTAL

Also propagate the patchset from 4.5.18 to 4.5.19.

debug/gdb: add latest version 7.0

cc/gcc: add latest 4.4.2 version as EXPERIMENTAL

kernel/linux: add latest versions

binutils: remove duplicate config entries for binutils & elf2flt

scripts: add sed expression to apply when renumbering patches

Some patchsets have superfluous members in their names (eg. the ones coming
from Gentoo), so it can come in handy to pass a sed RE to strip them out of
the final patch name.
Also add a 'fake' mode, where the command will only be printed and not
executed, so we can check beforehand if the rename will be OK.

scripts: fis addToolVersion wrt binutils

binutils' config file has moved; update the addToolVerion script accordingly.

kernel/linux: remove the version prompt

debug/gdb: remove old versions

config/binutils: remove obsolete experimental versions

config: rip-out versions marked as OBSOLETE

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.

1.5: update to 1.5.0+hg

Tagging release 1.5.1

1.5: update version to 1.5.1

arch/arm: add sample for nommu bare-metal Cortex-M3 with newlib

arch/arm: add THUMB interworking support

Add config option to build wtarget code with THUMB interworking.
This is used to build the C library as well as all other code
that runs on the target.

arch/arm: add THUMB mode config option

arch/arm: no need to check for the ABI option

The ABI option can not be set if EABI was selected,
so no need to check for it.

arch/arm: add support for noMMU

Some ARM cores do not have an MMU (eg. Cortex-Mx and Cortex-Rx series).
Thus, allow the user to configure out the MMU for ARM.

libc/newlib: allow using CVS snapshots

The newlib "team" rolls new releases about once a year (december).
This is quite a long time between releases, in case code was fixed.
So, allow user to use a CVS snapshot to benefit early from fixes
and enhancements to newlib.

functions: allow using sub-dir of a module

Some projects' module (eg. newlib) are checked-out into a sudirectory
rather than into their own directory. Handle this case in the CT_GetCVS
function.

libc/newlib: allow using newlib with archs other than avr32

libc/newlib: fix namespace in config file

C library config options should be prefixed with 'LIBC_'.

libc/newlib: cleanup the build and finish steps

build step:
- ./configure
- remove glibc-specific options
- pass the target CFLAGS in the correct variable
- make:
- build in //

finish step:
- print proper message in finish step

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

debug/dmalloc: fix handling of threading model

config: add help for the MMU/noMMU entry

config/libc: move around hidden config options

This yields a cleaner .config file that is easier to read.

scripts/functions: Fix a variable name.
Signed-off-by: Frederic Roussel <fr.frasc@gmail.com>
(transplanted from 991a59088ff09528896ac64ed4e8a6fba31eae39)

scripts/functions: Fix a variable name.
Signed-off-by: Frederic Roussel <fr.frasc@gmail.com>

config/arch/arm: default to EABI

docs: adding naming conventions for crosstool-NG

docs: fix chapter spacing

version: update to 1.5.0+hg

Merge.

scripts: replace calls to svn with calls to hg in script to renumber patches

docs: get rid of any reference to the now long-gone svn repository

docs: move the "contributing" section to overview.txt

docs: configure no longer accepts --with-contrib

It's been a while that configure does not recognise --with-contrib.
Applying contibutions is to be done manually, using patch.

configure: force using the C locale to check messages
(transplanted from 2f44fac6b5143f7b14f5367209c9df9b1102298e)

configure: fix --with-foo=/path/to/foo

When a required tool is specified with --with-foo, store the variable
in the list.
(transplanted from 1d43b65599a4b869d83d4db67b9715b1298d74f7)

configure: force using the C locale to check messages

configure: fix --with-foo=/path/to/foo

When a required tool is specified with --with-foo, store the variable
in the list.

eglibc: add support for user provided option groups

Signed-off-by: Arnaud Vrac <avrac@freebox.fr>

samples: fix the avr32-unknown-none sample

Bizarely enough, binutils-2.18 fails to build when CONFIG_SHELL is set
to /bin/bash (although it has code to recognise bash and act accordingly).

Waht is really strange is that it does build when CONFIG_SHELL is set
to /bin/sh, *although* /bin/sh is a symlink to /bin/bash. WTF?!?!
(transplanted from 56bba7d4fc8924d276b71134b7f1ef57bed57f52)

samples: fix the avr32-unknown-none sample

Bizarely enough, binutils-2.18 fails to build when CONFIG_SHELL is set
to /bin/bash (although it has code to recognise bash and act accordingly).

Waht is really strange is that it does build when CONFIG_SHELL is set
to /bin/sh, *although* /bin/sh is a symlink to /bin/bash. WTF?!?!

Tagging release 1.5.0

1.5: update version to 1.5.0

1.5: create maintenance branch for the 1.5 series

samples: update

libelf: add libelf-0.8.12

Merge.

configure: split has_or_abort in two: one to check, one to abort

Split the has_or_abort function in two:
- one that checks if the tool if found,
- one that calls the above check, and aborts if not found

The rational behind this is to be able to check for a tool
and if not found, fallback to using our bundled version,
should the need arise (and I get time).

Merge.

libc/glibc: don't use legacy snapshots

glibc snapshots have not been updated for about the
past 5 months. Consider them to be deprecated, now.

libc/glibc: remove dead code

The option to retrieve snapshots is already handled by
the generic 'specific date' and 'use latest' entries.
No need for a special case, as there's no code for it.

Merge.

debug/gdb: cleanup (remove) the static ncurses build

ncurses is built solely for the sake of building a native gdb.
The user should not rely on this library to build his/her userland,
but should rather build his/her own. So we remove it from the
sysroot after we successfully build the native gdb.

doc: update documentation, mostly eye-candy

sample: update the i686-nptl-linux-gnu sample

Update this sample, now it seems to correctly build again.

libc/eglibc: fix building for seemingly native toolchains

Build eglibc with -O2 as a fix/workaround to building
seemingly-native toolchains (see docs/overview.txt).

See:
- docs/overview.txt
- docs/known-issues.txt
- http://sourceware.org/ml/crossgcc/2009-10/msg00001.html

libc/glibc: fix building for seemingly native toolchains

Build glibc with -O2 as a fix/workaround to building
seemingly-native toolchains.

See:
- docs/overview.txt
- docs/known-issues.txt
- http://sourceware.org/ml/crossgcc/2009-09/msg00055.html

samples: upgrade some samples

Upgrading all samples is too much a hassle.
Stick with those few for now.

samples: remove arm-beagle-linux-gnueabi

Use the generic arm-cortex_a8-linux-gnueabi sample instead.

Merge.

scripts: update config.guess and config.sub

readme: document patch description

gcc: ecjx.cc -> ecjx.o should use host compiler, not cross compiler

gcc: forward port gcc-4.4.0 patchset to 4.4.1

kernel/linux: update versions.

Insert an empty line bwetween added new versions.

debug/ltrace: fix build with /exotic/ linux-host OS

For ARM EABI hosts (ct-ng's target), the tupple ends in 'gnueabi'
For uClibc-based toolchains, the tuple ends in '-uclibc.*'
Make ltrace recognise those tuples as being the same as 'linux-gnu'

Merge.

samples: correclty fix saving samples with a C library config file

samples: fix uClibc config file location

comp-libs/cloog: fix building

For CLooG/PPL 0.15.3, the directory name was simply cloog-ppl.
For any later versions, the driectory name does have the version, such as
cloog-ppl-0.15.4.

config: fix indentation for options marked EXPERIMENTAL or OBSOLETE

Change the 2-space separation into a 1-space separation, for the sake
of homogeneity.

scripts: add new version at top of choice

Add new versions at the top of the choice menu, not at the bottom.

config: re-order menu entries so that latest versions are at the top

It makes better sense to have latest versions at the top of the choice
entries.

Merge.

samples: update

comp-libs/mpc: add latest 0.7 version.

comp-libs/cloog: new versions have the version number in the dir name

For CLooG/PPL 0.15.3, the directory name was simply cloog-ppl.
For any later versions, the driectory name does have the version, such as
cloog-ppl-0.15.4.

samples: fix saving samples

Use a correct sed pattern when setting CT_PREFIX_DIR

libc/eglibc: fix download

Fix the test to check if download is forced.

Merge.

kernel/linux: add latest versions

Add 2.6.27.33 as long-term stable, and 2.6.30.6 and 2.6.31.

gcc: add patch to fix EABI for armv4t

As pointed out by Martin GUY, gcc incorrectly generates armv5t
instrcutions for EABI, even for cores that are an armv4t.
The new patch (for the 4.3 series) fixes the problem by downgrading
the default CPU for EABI to being an armv4t core.

kconfig: allow stdin/stdout redirection

Allow stdin/stdout redirection for the CLI conf (not mconf).
This allows to recall a sample and automatically apply the defaults
to new configuration option, with something like the following:
yes "" |ct-ng "sample_name"

docs: add a tutorial on how to build a toolchain on Mac OS-X

Add a step-bystep tutorial to build a cross-toolchain on Mac OS-X.

companion libs: add latest CLooG/PPL versions

Add the latest 0.15.{4,5,6,7} CLoog/PPL.

samples: show the PPL, GLoog/ppl and MPC versions

When displaying a sample, do show the PPL, CLoog/ppl and MPC versions

samples: fix displaying selected tools

Do display selected tools / debug facilities when displaying a sample.

samples: replace usage of echo with printf

Using printf instead of echo allows easier and better formatting.

tools wrapper: fix building

Remove the build tools only after the wrapper is built.
Use the corect C compiler to build the tools wrapper.
Use the correct log level.

crosstool.sh.in: better mesage when creating script-overrides

log functions: fix CT_DoLog and CT_DoExecLog

$@ and $* are different when in double quotes; use $* to print the message.

tools wrapper: move choice selection to a more appropriate place

Move the tools wrapper choice selection down to the companion libraries
sub-menu, to avoid the user going back and forth in the menu.

tools wrapper: fix config dependency

The tools wrapper is not needed only for canadian crosses, but also
for every other type of toolchain.

docs: typo in overview.txt

TODO: update

Add TODO list for m4, autoconf, automake and libtool.
Building our own versions would remove burden from the users
who have older versions on their distributions, and are not
ready/able/allowed to upgrade.

config.{gues,sub}: update

config: move the patch choice to the extract section

Choosing the origin of the patches to apply is best
done in the 'extract' section.

config: add fallback to patch order

Add the possibility to fallback to either bundled or local patches
if local or bundled are missing.

config: add the local,bundled patch order

This ordering first applies the local patches, then the bundeld ones.

config: make selecting the patch origin a choice rather than a bool

functions: do not over-detect error when patching

Merge.

tools wrapper: fix error due to unused argument

In the C wrapper, the argc argument is not used, causing an error
(as we treat warnings as errors). Use a dummy allocation to get
rid of the warning.

tools wrapper: correctly install the C wrapper

When building the C wrapper, specify the source file to be compiled.

config: move the "build shared libraries" option to the OS menu

The "Build shared libraries" config option is dependant on the type of
"Target OS".

Moving this options to the "Target OS" sub-menu is also better in the user
perspective: he/she no longer needs to go back and forth to see if he/she
missed any option.

config: make "Build shared libraries" depend on KERNEL_SUPPORTS_SHARED_LIBS

Now that all kernels that support shared libraries select the correct config
option, we can change the dependency rules of SHARED_LIBS accordingly.

config: Linux kernel selectes shared libraries support

The Linux kernel supports using shared libraries, so prompt the user.

config: introduce the KERNEL_SUPPORTS_SHARED_LIBS silent config option

The target OSes will be able to select this option if they support shared
libraries, instead of having "Build shared libaries" depend on each OS.

config: swap the debug and tools sub-menus

ltrace, in the debug sub-menu, selects libelf, in the tools sub-menu.
Inverse the order of the two sub-menus, so that the user does not have
to go back and forth between the two sub-menus.

config: move down companion libraries sub-menu

Move the companion libraries sub-menu down the main menu.
That way, the user does not need to go back and forth in the menu
to change options set by the different components that select the
companion libraries (binutils, gcc, gdb).

companion-libs: PPL/CLooG/MPC require GMP and MPFR

The PPL, CLoog/ppl and MPC libraries require GMP and MPFR.
Select GMP/MPFR appropriately.

tools wrapper: introduce the silent WRAPPER_NEEDED config option

Add the WRAPPER_NEEDED silent config option, that can be selected by
components that require it (companion libs so far).
Rely on this config option when deciding to install the wrapper,
instead of checking GMP/MPFR or PPL/CLoog/MPC.

Merge the C wrapper.

config: choose whether to use the shell or the C wrapper

Offer a config choice on whether to isntall the script wrapper, or
the compiled C wrapper. Update docs/overview.txt accordingly.

tool wrapper: add initial wrapper coded in C

Add an initial wrapper:
- find the realpath of the tool being called
- add the '.' in front of the tool name
- add the '/lib' dir to the base dir of the tool
- set and export LD_LIBRARY_PATH
- execve the real tool

overview: fix table of content, fix the hacker's way

table of content: add missing entry
the hacker's way: no need to "make install"

README: fix some space alignment

duma: fix downloading by forcing extension to .tar.gz

Downoading a non-existing file from sourceforge gives you a "200 OK"
and an index.html. As we try to retrieve a .tar.bz2 first, and duma
is bundled in a .tar.gz, we won't get appropriate content, so
just force the extension to avoid the problem.

Thanks to Ingmar Schraub <is@eseco.de> for pointing out the issue.

x86_64: is a MMU-aware arch, so select ARCH_USE_MMU

duma: fix version string.

DUMA uses '_' not '.' for major/minor/sub separation.

glibc: fix build error caused by incorrect variable assignment

During the conversion to using bash arrays, the glibc build script
was improperly converted, and contains an incorrect variable
assignment to the config_options array.

Merge the bash_array branch.

For every components where it makes sense, use bash arrays (instead
of a string with space-separated values) to store the options pased
to ./configure.

Allow setting --enable-cxx-flags on gcc ./configure

Some setups require one to pass extra CXX flags at the time of ./configure.
Make it easy.

Use bash arrays to store binutils config options

Make glibc's extra_config an array containing ./configure options

Change extra_config from a string to a array of options.

Make gdb's extra_config an array containing ./configure options

Change extra_config from a string to a array of options.

Make dmalloc's extra_config an array containing ./configure options

Change extra_config from a string to a array of options.

Make gcc's extra_config an array containing ./configure options

Change extra_config from a string to a array of options.

Make eglibc's extra_config an array containing ./configure options

Change extra_config from a string to a array of options.

configure: check for bash-3.1 or above

This is required to use the array variables that came with bash-3.1.

[libc-eglibc] Rewrite part of the code

Rewrite part of the code to better match the rest.
Most notably, rewrite handling of:
if [ ... ] && [ ... ]
to:
if [ ... -a ... ]

This has the positive side effect of calling "[" only once, although
"[" is probably a shell built-in.

[libc-eglibc] Fix testing for existing files

To test for existing files, use "[ -f blabla ]", not "[ -a blabla ]"
Checking for a file exsitence with "-a" is a bashism.
Althoug we _are_ using bash, it's disturbing as it can be misread as
the 'and' operator. Fix by using "-f".

samples: add eglibc-based toolchain for MIPS.

config: add Linux kernel 2.6.30.5

config: update Linux kernel long-term stable to 2.6.27.31.

Merge the AVR32 support branch to the default branch.

Removed debug line

Fix libc config

Misc AVR32 cleanups.

Changed copyright

Update README on how to send proper patches

Add a few lines of explanations on how to correctly setup
and use Mercurial to send proper patches.

Add sections to the README

Fix typo in README

Update the README with the new URL to the project homepage

The URL for the crosstool-NG homepage has changed. Update the
README accordingly. The old URL is still valid, though.

config/gcc: re-order versions

Move the gcc-4.3.4 version to its place.

gcc: add support for 4.3.4

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

gcc: add patch to fix PR37436

When compiling some C++ code, GCC 4.3.x fails with an internal
compiler error. The bug report is available at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37436. The included patch
is the one that has been merged in the trunk of gcc.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

config: make CONFIG_SHELL default to bash

Some components (eg. GMP) will fail to correctly build if
the CONFIG_SHELL is not bash (eg. ash or dash). So make bash
the default CONFIG_SHELL.

Keep ash as a possible selection, as future versions of those
currently /broken/ tools may come fixed wrt to CONFIG_SHELL
being POSIX-ly compliant.

Tagging release 1.4.2

1.4: update version to 1.4.2

[complib:mpfr] Fix building MPFR in some weird cases

The tmul test uses a compiled-in input file in $(srcdir).
The problem is that the Makefile passes it unquoted. The C code
tries to stringify it using clever macros, which may *usually* work.

In my case the source directory was named:
.../toolchain-powerpc-e500v2-linux-gnuspe-1.0-2.fc10/.../tests
And guess what? During testing I found out the program fails because
it tries to open:
.../toolchain-powerpc-e500v2-1-gnuspe-1.0-2.fc10/.../tests

Yes, CPP tokenized the macro before stringifying it and not surprisingly
the 'linux' part was converted to 1.
[on Fedora-10: cpp (GCC) 4.3.2 20081105 (Red Hat 4.3.2-7)]

So the attached patch simplify the macros and pass the path as string
from the Makefile.

Manually backported from 1449:8ad2773e7ae3

[configure] Fix automake version check

The configure script fails on automake-1.11 (in Fedora-11) since
it looks for 3-digit version number.

"Yann E. MORIN", added the following comment:

The check for the automake version is not against a 3-digit number,
but really against a 3-part version number, a-la 'x.y.z'. Versions
such as 1.10 and 1.11 are also valid.

Fix creating the .../lib/ directory structure in the non-sysroot case

The symbol link that is created in the sysroot directory only needs
to be made when the cross compiler is build with the sysroot option

Signed-off-by: Bart van der Meulen <bartvdrmeulen@gmail.com>
(transplanted from 0e49e6eddac4f5bbde6394eb3e6e36be75fc550c)

Also set CT_DEBUGROOT_DIR for non sysroot-ed toolchains.

In the non-sysroot-ed case, the debuf-root directory would not be set;
debug tools would have been installed God-only-knows-where...

Spotted by Bart van der Meulen <bartvdrmeulen@gmail.com>.
(transplanted from 634ffd14d936154464fd714ed29ed44c8e16ae02)

Add .hgignore file.

List all generated or temp files in .hgignore, so they
don't clutter the screen when running hg status.
(transplanted from befdb88324e18e1e80260906d0459a56ea0eb37a)

populate: fix installing dynamic linker 'ld.so'

The dynamic linker, ld.so, needs the execute bit to be set.
Detect tht the library being installed is in fact ld.so and
install it with 0755 instead of 0644.

Fix detecting src == dst.

Use a simpler command to copy src -> dst.

Also change echo to printf, get rid of 'echo -n', which is
highly non-portable.


-------- diffstat follows --------
/trunk/scripts/populate.in | 76 43 33 0 +++++++++++++++++++++++++++++-----------------------
1 file changed, 43 insertions(+), 33 deletions(-)
(transplanted from d7ddcb75e0f703e2ba6d17169167356389224870)

[configure] Use hg, instead of svn, to compute the version string

Now we moved from Subversion to Mercurial, use the hg command to
compute the version string.

Manually backported from 1409:7264ce426be4 plus 1430:933eee133cbf
as too much changes have been made to ./configure in the meantime.

[complib:mpfr] Fix building MPFR in some weird cases

The tmul test uses a compiled-in input file in $(srcdir).
The problem is that the Makefile passes it unquoted. The C code
tries to stringify it using clever macros, which may *usually* work.

In my case the source directory was named:
.../toolchain-powerpc-e500v2-linux-gnuspe-1.0-2.fc10/.../tests
And guess what? During testing I found out the program fails because
it tries to open:
.../toolchain-powerpc-e500v2-1-gnuspe-1.0-2.fc10/.../tests

Yes, CPP tokenized the macro before stringifying it and not surprisingly
the 'linux' part was converted to 1.
[on Fedora-10: cpp (GCC) 4.3.2 20081105 (Red Hat 4.3.2-7)]

So the attached patch simplify the macros and pass the path as string
from the Makefile.

[config] Merge CONFIG_SHELL selection.

[config] Warn againt using ash as CONFIG_SHELL

It apears that more and more ./configure scripts and Makefiles
make use of non-POSIXly correct shell constructs, that don't
work with ash.

For now, just warn the user against using ash, but keep it as
an option in case newer versions of the /broken/ components
come fixed, and we can again use ash, as it is in some cases
really faster than bash.

[config] Allow user to specify custom CONFIG_SHELL

In case the shell the user wants to use as CONFIG_SHELL is located in a
weird place (eg. /opt/bash/bin/bash), or is weirdly named (eg. bash-4),
let the user enter the patch to the shell.

[config] Add bash as a possible CONFIG_SHELL

On some systems and/or for some components, it may be necessary to
explicitly use bash as the shell used by ./configure and Makefiles.

[config] Change the way to select the CONFIG_SHELL

Transform the single boolean option to a 'choice' selection
with two options: "sh" and "ash".

This is needed to later add "bash" as override.

Merge the queue with all new component versions.

[cc-gcc] Add latest versions

Add gcc-4.4.1

[scripts-add-version] Handle gcc 4.4+

Handle gcc-4.4+ when adding a new gcc version.

[comp-lib-gmp] Add latest versions

Add 4.3.0 and 4.3.1.

[tools-libelf] Add latest version.

Add libelf 0.8.11, propagate patchset from 0.8.10.

[libc-eglibc] Add latest version

Add latest branch 2_10.

[debug-ltrace] Add latest version.

Add ltrace 0.5.2, propagate patchset from 0.5.1 and from Debian.

[debug-duma] Add latest versions

Add 2.5.15, propagate patchset from 2_5_14 up to 2_5_15.

[kernel-linux] Add latest versions

Add 2.6.29.{5,6} and 2.6.30{,.1}
Update 2.6.27.24 to 2.6.27.26 as long-term stable.

fix wrapper script for symlinks

The wrapper script placed around the target binaries when
using the companion libraries does not work for symbolic links
The wrapper scripts needs to follow the links before calling the
actual binary

Signed-off-by: Bart vdr. Meulen <bartvdrmeulen@gmail.com>

---

Add g++ to required tools

Because gmp is now always build with --enable-cxx,
g++ has become a required tool

Signed-off-by: Bart vdr Meulen <bartvdrmeulen@gmail.com>

---

[configure] Fix automake version check.

The configure script fails on automake-1.11 (in Fedora-11) since
it looks for 3-digit version number.

Patch fixed by "Yann E. MORIN", with the added comment:

The check for the automake version is not against a 3-digit number,
but really against a 3-part version number, a-la 'x.y.z'. Versions
such as 1.10 and 1.11 are also valid.

Require GNU awk at ./configure time.

Some components (specifically {,e}glibc) will not build when awk
is not GNU awk. Make ./configure check for GNU awk.

Make it build again for non-local use.

Using colons (:) in the version string creates Makefile problems:

Makefile:195: *** multiple target patterns. Stop.
make: *** [build] Error 2

Merge the canadian branch to default.

Now the preliminray support for canadian-crosses is done,
merge to default. The few remaining quirks, if any, will
be resolved on mainstream.

[samples] Add a linux -> mingw32 -> i686-linux canadian sample

Add a sample that builds on Linux a mingw32-hosted toolchain that
generates code for i686-none-linux-gnu.

Signed-off-by: Bart van der Meulen <bartvdrmeulen@gmail.com>

[samples] Don't mix canadian samples with non-canadian ones.

- save the canadian smples in their own way, so as not to
mix non-canadian samples with canadian ones
- list canadian samples with the host information

Cleanup the handling of canadian settings

Bring handling the 'canadian' settings as par with the existing
'cross' settings.