buildroot-novena/toolchain/gdb, branch 2012.11_rc1

gdb: not available on aarch64 for the target

2012-11-16T21:25:40Z

Fixes http://autobuild.buildroot.org/results/d32a0fb1584a125cccde521a3960fb87ff7e2de6/build-end.log Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

toolchain/gdb: disable support of full gdb on target for blackfin

2012-11-15T23:28:40Z

There is no support in gdb 6.6 for the Blackfin architecture, so disallow this choice. This fixes the following build failure: http://autobuild.buildroot.org/results/e37db29810265a756833da163fda444d967d7874/build-end.log Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

xtensa: support configurable processor configurations

2012-11-15T15:39:48Z

Xtensa is a configurable processor architecture, which allows to define additional instructions and registers. The required variant specific information for the toolchain is delivered in an 'overlay' file, which needs to be 'untarred' to the corresponding directories after the source is installed and patched. This patch provides support for binutils, gcc, and gdb with a very limited changes to the build scripts. These additions are only executed for the Xtensa architecture and have no effect on other architectures. [Thomas: rebased on top of the 'arch: improve definition of gcc mtune, mcpu, etc.' patch, and changed 'Target ABI' to 'Target Architecture Variant']. Signed-off-by: Chris Zankel Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

gdb: adjust behavior when thread debug is not available

2012-11-03T16:51:29Z

When an external toolchain without thread debug is used, the gdb package can be selected, but no version can be choosen, since none match any of the requirements. This leads Buildroot to try to build gdb for the target without a version being defined, as in the following build log: http://autobuild.buildroot.org/results/84e8fd2df0cc22448052a572c2e9a6e03dd137eb/build-end.log To fix this, we adjust the dependencies of the BR2_PACKAGE_GDB option so that the package as a whole is not selectable when the required conditions are not met. Basically, we have the choice of: * Having a toolchain that supports thread debugging, which is needed for gdb >= 7.x * Having BR2_DEPRECATED enabled, which allows gdb 6.8 to be selected, which doesn't require thread debugging * Using bfin, since this architectures has a special old gdb version Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

gdb: target gdb not available on microblaze

2012-10-14T18:14:39Z

Fixes http://autobuild.buildroot.org/results/5950c95ca12721dd910ad72fe52bfa9ac45a5120/build-end.log Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

Remove the Xtensa architecture

2012-09-20T20:31:08Z

As stated in commit 555c2585bf28c3ef71f6d2dcdd983d17a19892af, the Xtensa architecture has been introduced in 2009 and never changed since its initial introduction. It requires some special handling that is a bit annoying, and despite our call to the initial developers, and the announcement of the deprecation of the architecture during the 2012.05, nothing has happened. Therefore, drop support for this architecture. Signed-off-by: Thomas Petazzoni Acked-by: me Signed-off-by: Peter Korsgaard

toolchain: reinstate host/usr/bin/$arch-linux-* symlinks for gcc/gdb binaries

2012-06-23T19:33:17Z

As people might be using them. Signed-off-by: Peter Korsgaard

Remove REAL_GNU_TARGET_NAME

2012-06-23T13:14:51Z

Instead of providing two variables, make GNU_TARGET_NAME give the real target name, and remove REAL_GNU_TARGET_NAME altogether. Signed-off-by: Richard Braun Signed-off-by: Peter Korsgaard

gdb: not available on avr32

2012-05-14T20:36:53Z

Fixes http://autobuild.buildroot.org/results/1c6cfa7f069e2b7d8a7dacf76fbf95b7909fb37a/build-end.log. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

gdb: fix target gdb build when host-gawk is built before

2012-05-07T19:40:31Z

When the crosstool-ng backend is used, host-gawk is built as a dependency of the crosstool-ng package, and therefore an host 'gawk' binary is installed in $(HOST_DIR). When the target gdb package is also selected, this unfortunately leads to a build failure, as reported on http://buildroot.humanoidz.org/results/f19c0499d08212d8b5100fa9434e1197092957db/build-end.log. The problem is that the ./configure of gdb detects gawk in the PATH, but at compile time, it fails to find gawk. This is due to the fact that the gdb compilation process is started without the correct path. This patch fixes this by passing $(TARGET_MAKE_ENV) in the environment of the gdb compilation process. A better fix would be to switch gdb to the AUTOTARGETS infrastructure in the future. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard