We add the wchar stuff at compile time using sed, so the default defconfig
works, the file hasn't seen any updates since it first got committed, and
there's no references to it in the tree.
As discussed on the list. I suspect the ARM abi thing isn't needed anymore
now we use the correct abi in the first place, but I'll leave it in until
after the release.
I know that changing something as fundamental as mpfr this close to the
release isn't really ideal, but it's listed as the minimum version
for gcc 4.3.x:
http://gcc.gnu.org/install/prerequisites.html
Bernhard's tree has been using 2.3.2 since October, so the risk is probably
not that big though.
that the options become visible just below
the config, instead of at bottom of screen
Create a more useful default as toolchain path.
Allow generation of a script which sets up
paths to a binary toolchain generated by buildroot.
features.h (or something including it) is needed for __UCLIBC* to get
defined - E.G. without that the build breaks without largefile support.
Nigel, what was the reason for your commit and what file not found error
did you see?
Revert to the -35 debian patch (from stable.debian.net) so the other
patches apply, E.G. effectively revert r23968.
Someone who actually uses grub should probably look into updating our
version.
"target/device/Atmel/arch-avre/kernel-headers-2.6.28.2"
Make sure BR2_KERNEL_HEADERS_PATCH_DIR is enabled for 2.6.28
Set
KERNEL_HEADERS_PATCH_DIR="target/device/Atmel/arch-avre/kernel-headers-2.6.28.2"
for Atmel AVR32 targets and "valka"
Have added options that mean you can set the same BR2_XXXX variables
for external toolchain and internal (buildroot built) toolchain.
This means the same set of packages can be built now me as for you.....
Signed-off-by: Daniel Laird <daniel.j.laird@nxp.com>
The GNU_TARGET_NAME symlink and target_utils location were not correctly
adjusted to match the move of the toolchain to $(STAGING_DIR)/usr,
creating dangling symlinks.
Make sure the developer is informed why a package is not
visable and that they need to have a NPTL enabled
toolchain.
Signed-off-by: Daniel Laird <daniel.j.laird@nxp.com>
