buildroot-novena/toolchain/Config.in.1, branch 2010.11_rc2build system for the novena open hardware laptop boardhttps://git.bnewbold.net/buildroot-novena/atom?h=2010.11_rc22010-07-28T14:20:08Ztoolchain: move buildroot config files2010-07-28T14:20:08ZYann E. MORINyann.morin.1998@anciens.enib.fr2010-07-27T22:08:16Zurn:sha1:2508b16d66cd26065af4b06576df9646a1ffdb18
Handle the internal toolchain backend mechanism the
same way we handle other backends.
Signed-off-by: Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Use BR2_TOOLCHAIN_BUILDROOT instead of BR2_TOOLCHAIN_SOURCE2009-12-14T22:54:47ZThomas Petazzonithomas.petazzoni@free-electrons.com2009-12-14T11:10:12Zurn:sha1:bc994c533cdac1ab843a889c4afaae80234cc6b2
The BR2_TOOLCHAIN_SOURCE option is removed in a future commit.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
toolchain: use same gdb Config.in for internal/external toolchains2008-12-15T15:28:48ZPeter Korsgaardjacmet@sunsite.dk2008-12-15T15:28:48Zurn:sha1:e2e4950b2d9334e6380e32cf30c7c7968747ccc0
We used to use different gdb configs for internal and external toolchains
because mconf won't source the same file twice. This works, but is kind of
sub optimal, as people forget to keep them in sync.
Fix it to use the same file for both situations by shuffling around the
config options a bit. Should work identical to before (except for the newer
gdb versions available for ext).