buildroot-novena/toolchain/toolchain-crosstool-ng, branch master

Introduce BR2_TOOLCHAIN_USES_{UCLIBC, GLIBC}

2013-07-04T07:08:42+00:00

Currently, when we need to do a conditional on the type of C library used, we need to take into account the three toolchain backends. As we are going to add eglibc support to the Buildroot toolchain backend, it would become even uglier, so this patch introduces two new hidden options: BR2_TOOLCHAIN_USES_UCLIBC and BR2_TOOLCHAIN_USES_GLIBC, that exist regardless of the toolchain backend. The entire Buildroot code base is converted to use those options. Note that we have intentionally created only one option (BR2_TOOLCHAIN_USES_GLIBC) for both glibc and eglibc, since they are essentially the same, as far as Buildroot is concerned. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

Use more sensible names for the external/ctng targets

2013-07-03T22:14:10+00:00

Instead of using the 'uclibc' target for all toolchain backends, introduce more sensible target names for the external toolchain and Crosstool-NG toolchain backend make targets. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

uclibc: convert to the package infrastructure

2013-07-03T22:13:23+00:00

[Peter: update manual to match] Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

gdb: convert to the package infrastructure

2013-04-11T19:46:32+00:00

This commit converts gdb to the package infrastructure, and therefore moves it from toolchain/gdb to package/gdb. The target package is now visible in "Package selection for the target" => "Debugging, profiling and benchmark". The main option, "gdb", forcefully selects the "gdbserver" sub-option by default. Another sub-option, "full debugger" allows to install the complete gdb on the target. When this option is enabled, then "gdbserver" is no longer forcefully selected. This ensures that at least gdbserver or the full debugger gets built/installed, so that the package is not a no-op. The host debugger is still enabled through a configuration option in "Toolchain". It is now visible regardless of the toolchain type (it used to be hidden for External Toolchains). The configuration options relative to the host debugger are now in package/gdb/Config.in.host, similar to how we have package/binutils/Config.in.host. Since gdb is now a proper package, it is no longer allowed to 'select BR2_PTHREADS_DEBUG' to ensure thread debugging is available when needed. Instead, it now 'depends on BR2_TOOLCHAIN_HAS_THREADS_DEBUG'. This option, in turn, is selected by the different toolchain backends when appropriate. The 'BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED' option is removed, since we no longer need to know when it is allowed to 'select BR2_PTHREADS_DEBUG'. Also, the 'BR2_PTHREADS_DEBUG' option is moved to appear right below the thread implementation selection (in the case of the Buildroot toolchain backend). Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

toolchain/crosstool-NG: do not depend on the top-level Buildroot's .config

2013-03-18T22:16:54+00:00

Previously, the crosstool-NG backend did depend on the top-level Buildroot's .config to detect changes in the toolchain options, using a tentatively-clever heuristic, which also included the full Buildroot's version string to push down to set the components' versions strings. In doing so, any commit in the Buildroot tree would imply a complete rebuild of the toolchain, even in the case the toolchain options did not change, thus being a large annoyance (to say the least). As Buildroot never guaranteed that toolchain options would be detected, even less handled, and that the internal backend does neither detect nor act on toolchain options changes, and delegate that to the user, there is no point in individualising the crosstool-NG backend's behaviour. This reasoning also applies to the depdency on the crosstool-NG's bundled .config file, too. So, just drop the not-so-clever heuristic, and just build the toolchain once, leaving to the user the responsibility to explictly ask Buildroot to rebuild the toolchain. Reported-by: "Przemyslaw Wrzos" Signed-off-by: "Yann E. MORIN" Cc: "Przemyslaw Wrzos" Cc: Thomas Petazzoni Signed-off-by: Peter Korsgaard

toolchain/crosstool-ng: sprinkle with some calls to MESSAGE

2013-01-20T21:10:44+00:00

Thus, the failing step can be easily extracted by autobuilders, to ease with post-mortem analysis. At the same time, remove two debug echoes (Arnout). Signed-off-by: "Yann E. MORIN" Acked-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard

toolchain/crostool-ng: use newly-introduced BUILDROOT_CONFIG

2013-01-13T22:15:07+00:00

No need to recreate a path we already have. Signed-off-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

toolchain/crosstool-ng: be more explicit in the config file help

2013-01-12T20:48:05+00:00

Some users seem to interpret: make ctng-menuconfig as being a value that can be fit for the ct-ng config file. Clarify that it is a command to run, not a possible value. Reported-by: Thomas Petazzoni Signed-off-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

Fix installation of crosstool-ng libraries to target

2013-01-06T11:13:20+00:00

When using the crosstool-ng toolchain option, the libc libraries were not installed to target. Buildroot calls the show-tuple function to determine the directory to copy from, and it seems that outputs the result to stderr instead of stdout Signed-off-by: Floris Bos Acked-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

toolchain/crosstool-ng: update config for glibc-based toolchains

2012-12-21T08:18:33+00:00

Update the version of glibc to be used, since older versions are broken with the currently-used binutils versions. Fixes build issues ending with: tmpfs/ccvkz3ro.s:33: Error: CFI instruction used without previous .cfi_startproc This new version does not have RPC support, so update the Config.in. CC: Thomas Petazzoni Signed-off-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard