summaryrefslogtreecommitdiff
path: root/toolchain/Config.in.2
AgeCommit message (Collapse)Author
2010-06-15Fix potentially conflicting build flagsPaul Jones
Change the default target optimisation value so it does not conflict with gcc optimization level Signed-off-by: Paul Jones <paul@pauljones.id.au> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-05-24Improve gettext integrationThomas Petazzoni
Having a BR2_NEEDS_GETTEXT option, as introduced by 54d64798e1e14b526c3cc1142961972cff9f1e8a isn't sufficient to express the different kind of dependencies on gettext. This commit, based on an idea by Peter Korsgaard, introduces two different options : * BR2_NEEDS_GETTEXT, which is true as soon as the toolchain doesn't provide gettext itself (i.e, when the toolchain is uClibc based, be it an internal or external toolchain) * BR2_NEEDS_GETTEXT_IF_LOCALE, which is true when the toolchain doesn't provide gettext *and* locale support has been enabled in Buildroot. A following commit adds some documentation that details how these configuration variables should be used by packages. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-05-20Add a BR2_NEEDS_GETTEXT optionThomas Petazzoni
When using an external toolchain that uses the glibc or eglibc C libraries, compiling a separate gettext and libintl is not needed and is even a source of confusion, causing build failures. These build failures are due to the fact that when libintl is compiled, it replaces the C library libintl.h by its own, which does #define gettext libintl_gettext. Then, when packages want to use gettext, autoconf realize that gettext is available in the C library and therefore do not add -lintl to the LDFLAGS, causing the build failure because the program has been compiled to use libintl_gettext but this function is not available. Therefore, we should only use gettext if a uClibc internal toolchain or a uClibc external toolchain. If an external glibc toolchain is used, gettext shouldn't be used. In order to implement that, we introduce the BR2_NEEDS_GETTEXT option, which is hidden to the user, and whose value is computed automatically from the rest of the configuration. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-04-11Remove BR2_ENABLE_LOCALE_PREGENERATEDThomas Petazzoni
The option is marked broken since october 2009, and even the uClibc configuration help text says that using pregenerated locales is highly discouraged. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-03-30get rid of broken nios2 supportPeter Korsgaard
Has been marked as broken for more than 1 year, with no indication that anyone cares, and it needs a bunch of special handling. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-02-23uclibc: do not allow the selection of NPTL if snapshot is not selectedThomas Petazzoni
In uClibc, NPTL support does not exist in the 0.9.30 branch, that we are using in Buildroot. It is only available in the uClibc daily snapshot, extracted from uClibc master branch. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2009-12-14Use BR2_TOOLCHAIN_BUILDROOT instead of BR2_TOOLCHAIN_SOURCEThomas Petazzoni
The BR2_TOOLCHAIN_SOURCE option is removed in a future commit. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2009-11-09toolchain: select sensible floating point mode by defaultPeter Korsgaard
Introduce BR2_PREFER_SOFT_FLOAT and enable it for arm, avr32 and mips, and use it to enable soft float support by default for those archs. This way people automatically get the correct floating point mode when running make menuconfig for the first time (E.G. without a .config) and changing the arch from i386 to arm/avr32/mips. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2009-10-22toolchain: mark BR2_ENABLE_LOCALE_PREGENERATED as brokenPeter Korsgaard
There's still no suitable tarball available on uclibc.org, so better hide the option for now. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2009-07-31Fix PROGRAM_INVOCATION handling with external toolchainsThomas Petazzoni
BR2_UCLIBC_PROGRAM_INVOCATION is a toolchain configuration option, like BR2_INET_IPV6, BR2_INET_RPC, on which some packages depend. Therefore, it should be handled like BR2_INET_IPV6 and BR2_INET_RPC in order to work properly with external toolchains. Since we move it out of toolchain/uClibc/Config.in into toolchain/Config.in.2, we rename the option to BR2_PROGRAM_INVOCATION (since BR2_INET_RPC and others don't have UCLIBC in their name). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2009-07-27toolchain: Clean up locale support menuWill Newton
Closes #421. This patch cleans up and fixes some minor issues with the locale support section of the toolchain menu. 1. uClibc requires wchar support if locales are enabled, make locale support select wchar support. 2. Allow purging of locale information even if there is no locale support in the C library. This cleans up after packages that install things into /usr/share/locale on the target. Signed-off-by: Will Newton <will.newton@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2009-04-22toolchain: add BR2_USE_SSP option for stack protection supportPeter Korsgaard
Using the support in uClibc.
2009-04-06Makefile: add BR2_ENABLE_LOCALE_PURGE to purge unwanted localesPeter Korsgaard
Add BR2_ENABLE_LOCALE_PURGE / BR2_ENABLE_LOCALE_WHITELIST options to remove unwanted locales from the target rootfs. Handy for stuff like the gtk stack, which comes with ~25 MB locales. Works similar to localepurge in Debian, E.G. you provide a white list of wanted locales, and everything else is removed.
2009-01-30Extend External Toolchain options (match buildroot built toolchain): Daniel Laird
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>
2009-01-18The liboil Makefile will use "-mcpu=vfp" when building for ARM.Ulf Samuelsson
The VFP is only available for a few ARM CPUs at the moment, so this breaks the liboil build. A patch is available upstream which only enables "-mfpu=vfp" if "--enable-vfp" is given to "configure". Autotools needs to be run for liboil for this to take effect. A new configuration BR2_VFP_FLOAT is added to allow enabling vfp. If this is "yes", then "-mfpu=vfp" is added to CFLAGS.
2008-12-15toolchain: use same gdb Config.in for internal/external toolchainsPeter Korsgaard
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).
2008-11-03External toolchain support improvementsPeter Korsgaard
Improve external toolchain support * Do not put kernel-headers in the dependencies of BASE_TARGETS in the case where BR2_TOOLCHAIN_SOURCE is not y. The kernel headers are already supposed to be part of the external toolchain, so there's no need to download, extract and install them. * In the configuration system, don't display the kernel headers version selection list when an external toolchain is selected. This is implemented by moving the source "toolchain/kernel-headers/Config.in" inside the if BR2_TOOLCHAIN_SOURCE in toolchain/Config.in.2. * Change the description and help message of the BR2_LARGEFILE, BR2_INET_IPV6, BR2_INET_RPC, and BR2_SOFT_FLOAT option in toolchain/external-toolchain/Config.in. In the case of an external toolchain, the semantic of these options is not to enable large file support, IPV6 or RPC (since the toolchain is already compiled, it has been decided previously). Their semantic is to let Buildroot know about the characteristics of the external toolchain being used. As an improvement, we could guess these values automatically: - for BR2_LARGEFILE, look at the value of __UCLIBC_HAS_LFS__ in bits/uClibc_config.h in the libc headers directory. - for BR2_INET_RPC, look at the value of __UCLIBC_HAS_RPC__ in the same file - for BR2_INET_IPV6, look at the value of __UCLIBC_HAS_IPV6__ in the same file - for BR2_SOFT_FLOAT, look at the output of $(CC) -v 2>&1 | grep -- "--with-float=soft" But I'm not sure how this would be possible, since these values are used at configuration-time by other configuration options, not only at build time. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2008-07-17Kconfig: remove 'default n'Peter Korsgaard
'default n' is the default, so there's no need to say it explicitly.
2008-06-16toolchain: move elf2flt+mklibs under 'Common Toolchain Options'Peter Korsgaard
2008-06-13toolchain: also setup kernel headers when ext toolchain is usedPeter Korsgaard
Provide kernel headers when ext toolchain is used, so we can compile packages which need them.
2007-11-09update gcc nios2 support, thanks atleIvan Kuten
2007-10-23Ensure AVR32 FPU config is always correctUlf Samuelsson
2007-10-05- adjust default for LFSBernhard Reutner-Fischer
2007-09-26- revert some bad checkins, fixup bad settings in atmel targets and move the ↵Bernhard Reutner-Fischer
gcc target abi back to a place where the other arch-specific settings live
2007-09-25- revert patch that obfuscates the config UI and doesn't reflect the order ↵Bernhard Reutner-Fischer
of config steps
2007-09-24Reorganize configs to even more logical positionsUlf Samuelsson
2007-09-22- Subsume and collaps toolchain options in one menuBernhard Reutner-Fischer
This is ment to ease configuration by providing toolchain related options in one place No functional changes, just shuffling the menus around..
2007-07-31Change def of BR2_USE_WCHAR to build uClibc w WCHAR supportUlf Samuelsson
2007-07-07- improve help textBernhard Reutner-Fischer
2007-06-26- add BR2_INET_IPV6 and BR2_INET_RPCBernhard Reutner-Fischer
TODO: use $(DISABLE_IPV6) in packages instead of a gazillion different hackish ways that are currently in there
2007-02-06Support building using an external toolchain. Questions to the mailing list ↵"Steven J. Hill"
and all other comments to <biteme@devnull.com>.