Update the configuration and the comment.
Reported-by: Anthony Foiani <anthony.foiani@gmail.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Both toolchains were tested to successfully:
- _build_ busybox, giving respectively an n32 and an n64 binary
although it has not been run-tested.
- build linux-2.6.36-rc3 for Loongson, giving an n64 vmlinux
(which is expected, due to the way the kernel is built),
and the kernel properly boots!
Credits are due to Julien MOUTHINO (julm on freenode#uClibc) for
testing that the kernel boots on his hardware! Cheers! ;-)
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
- 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
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>
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 ...
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.
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?!?!
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>
