summaryrefslogtreecommitdiffstats
path: root/toolchain/Config.in
Commit message (Collapse)AuthorAgeFilesLines
* eglibc: enable support in the Buildroot toolchain backendThomas Petazzoni2013-07-041-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | Using the newly introduced 'eglibc' package, this commit enables the option of building a toolchain using the eglibc C library in the Buildroot toolchain backend. In details, this commit: * Creates a choice to select uClibc or eglibc in the Buildroot toolchain backend (in toolchain/toolchain-buildroot/Config.in), and removes the fact that the Buildroot toolchain backend forcefully enables uClibc (toolchain/Config.in). * Creates a BUILDROOT_LIBC variables, which points to the package implementing the C library (i.e either 'uclibc' or 'eglibc'). * Modifies the gcc-final and gcc-intermediate makefiles to use the BUILDROOT_LIBC variable instead of hardcoding the use of uclibc. * Ensures that TLS support is always enabled when building eglibc. [Peter: fix commit text to refer to BUILDROOT_LIBC] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* Introduce BR2_TOOLCHAIN_USES_{UCLIBC, GLIBC}Thomas Petazzoni2013-07-041-0/+16
| | | | | | | | | | | | | | | | | 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 <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* toolchain/crostool-NG: mark as deprecatedYann E. MORIN2013-05-071-0/+1
| | | | | | | | | | | | | | | | | | | | | | For the following reasons: - it used to be broken without anyone noticing for a long time, - it is still not fully integrated within the Buildroot set of options, - it has not gained much traction (not even I use it), - I've always argued that sustained development should use an external toolchain, and not rely on building one with Buildroot, - I did not submit any of the enhancements requested during the last developpers' day in Brussels, - I have neither the incentive nor the time to maintain and enhance it, it is time to deprecate the crosstool-NG backend for the 2013.05 release. Then, it will be entirely removed early in the 2013.08 cycle, to let some time for those that rely on it to voice their opinions. ;-) Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Peter Korsgaard <jacmet@uclibc.org> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* arc: disable Crosstool-NG for ARCMischa Jonker2013-05-041-1/+1
| | | | | Signed-off-by: Mischa Jonker <mjonker@synopsys.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* gdb: convert to the package infrastructureThomas Petazzoni2013-04-111-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* toolchain: update crosstool-NG project URLThomas Petazzoni2013-03-241-1/+1
| | | | | Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* xtensa: add support for the Xtensa architectureChris Zankel2012-11-151-1/+1
| | | | | | | | | | | | | The Xtensa architecture had been removed because it required special handling and depended on additional directories and files that became obsolete over time. This change is more aligned to other architectures. [Thomas: rebased on top of the "arch: improve definition of gcc mtune, mcpu, etc." patch]. Signed-off-by: Chris Zankel <chris@zankel.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* toolchain: make external toolchain the default for AArch64Thomas Petazzoni2012-11-021-2/+2
| | | | | | | | | | Our internal toolchain backend does not yet have support for AArch64, and Crosstool-NG also does not have support for AArch64 at the moment (though it should be coming quickly since the Linaro AArch64 toolchain is generated with a modified Crosstool-NG version). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* toolchain: disallow internal/ctng toolchains for microblazePeter Korsgaard2012-03-191-0/+2
| | | | | | | | While there's some microblaze support in mainline gcc from 4.6.x, there still seems to be something missing with the uClibc support, so disable these for now. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* gdb: fix kconfig dependency handling with !BR_TOOLCHAIN_BUILDROOTPeter Korsgaard2011-11-241-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Newer versions of GDB need pthread debugging support if threads are enabled, which is always the case for glibc but is a configure option for uClibc. We have solved this for internal toolchains by selecting the BR2_PTHREAD_DEBUG option from the GDB selection if needed, but as this option isn't available when ctng/external toolchains are used, mconf prints ugly warnings and the build may fail if an external uClibc toolchain without pthread debugging support is used. Fix it by introducing 2 more hidden config options: - BR2_TOOLCHAIN_HAS_THREADS_DEBUG - BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED The first tells us if the toolchain HAS pthreads debugging support, and is checked by check_uclibc_feature in helper.mk for external uClibc based toolchains. The second tells us if the toolchain is ABLE TO provide pthreads debugging support if threads are enabled, either because it's an internal toolchain where we can force enable it or an external glibc/eglibc toolchain or uClibc with the option enabled. Crosstool-ng forcibly enables this support, so those will always work. The preconfigured uClibc-based toolchains we have also all enable it. Finally, show a comment if this isn't the case so the (external toolchain) user knows why. This is placed outside the choice option, as menuconfig has a bug where it doesn't show choice selections which only contain comments. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* toolchain: introduce BR2_TOOLCHAIN_HAS_SHADOW_PASSWORDSThomas Petazzoni2011-06-121-0/+2
| | | | | | | | | | | | | | | Unfortunately, the official Blackfin toolchains are built without the shadow password support, so our default Busybox configuration fails to build. Therefore, we introduce a new hidden knob BR2_TOOLCHAIN_HAS_SHADOW_PASSWORDS, which is set to yes for Buildroot internal toolchain, for toolchains generated by the Crosstool-NG backend, for Glibc external toolchains and for Uclibc custom external toolchains. It is left unset by the Blackfin toolchain profile. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* toolchain: add support for external toolchain profiles and downloadThomas Petazzoni2010-12-131-1/+4
| | | | | | | | | | | | | | | | | | | Instead of letting the user define all the details of his external toolchain, we define a set of profiles for well-known external toolchains (CodeSourcery ones only at the moment, can easily be extended with other toolchains). Once a profile has been choosen, the user is offered the choice of either letting Buildroot download and install the external toolchain, or (as before) to tell Buildroot where the toolchain is installed on the system. We of course provide a "custom profile", through which the user can configure Buildroot to use a custom external toolchain for which no profile is available. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* toolchain: add new toolchain backend: crosstool-NGYann E. MORIN2010-10-011-0/+9
| | | | | | [Peter: indent Config.in, shuffle make targets around] Signed-off-by: Yann E. MORIN <yann.morin.1998@anciens.enib.fr> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* toolchain: move buildroot config filesYann E. MORIN2010-07-281-9/+3
| | | | | | | | 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>
* toolchain: rename external toolchain dirYann E. MORIN2010-07-281-2/+2
| | | | | | | | | Rename the external toolchain directory. When new backends are here, it will be easier to sort them out if they are all prefixed the same way. Signed-off-by: Yann E. MORIN <yann.morin.1998@anciens.enib.fr> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* toolchain: get rid of "binary" for external toolchainPeter Korsgaard2010-02-081-1/+1
| | | | | | | We no longer have an option for external source based toolchains, so get rid of "binary". Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* Remove external source toolchain optionsThomas Petazzoni2009-12-141-12/+0
| | | | Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* toolchain: revert r25193 (Change binary toolchain configuration)Peter Korsgaard2009-02-041-3/+1
| | | | As discussed on the list.
* Change binary toolchain configuration, soUlf Samuelsson2009-01-311-1/+3
| | | | | | | | | | | 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.
* toolchain: revert "Allow creating a script for external use of Buildroot ↵Peter Korsgaard2009-01-021-2/+0
| | | | | | toolchain" It's been 10 days now without any reply from Ulf, so revert r24480+r24481.
* Allow creating a script for external use of Buildroot toolchainUlf Samuelsson2008-12-211-0/+2
|
* toolchain: use same gdb Config.in for internal/external toolchainsPeter Korsgaard2008-12-151-1/+10
| | | | | | | | | | 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).
* buildroot: remove trailing spacesPeter Korsgaard2008-08-041-1/+1
| | | | | | | for i in `find -name 'Config*' -o -name 'Makefile*' -o -name '*.mk'`; do sed -i 's/ \+$//' $i; done
* Remove duplication of AVR32 toolchainUlf Samuelsson2008-03-291-1/+3
|
* toolchain updatesJohn Voltz2008-03-061-4/+2
|
* - naming convention is Config.in resp. Config.in.fooBernhard Reutner-Fischer2007-09-281-1/+1
| | | | Adjust some accordingly
* - revert some bad checkins, fixup bad settings in atmel targets and move the ↵Bernhard Reutner-Fischer2007-09-261-4/+17
| | | | gcc target abi back to a place where the other arch-specific settings live
* reinstate AVR32 toolchainUlf Samuelsson2007-09-261-15/+3
|
* - add more help textBernhard Reutner-Fischer2007-09-251-0/+3
|
* - fix copy'n paste errorBernhard Reutner-Fischer2007-09-251-1/+1
|
* - remove one invariant in toolchain type selection.Bernhard Reutner-Fischer2007-09-251-3/+12
|
* - move project settings from toolchain to deviceBernhard Reutner-Fischer2007-09-221-2/+0
|
* - Subsume and collaps toolchain options in one menuBernhard Reutner-Fischer2007-09-221-7/+7
| | | | | This is ment to ease configuration by providing toolchain related options in one place No functional changes, just shuffling the menus around..
* - fixup whitespace damage after ulfBernhard Reutner-Fischer2007-08-211-1/+1
|
* Add support for prepatched toolchainsUlf Samuelsson2007-07-311-2/+5
|
* Get rid of leading whitespace to silence warnings from config system."Steven J. Hill"2007-07-061-1/+1
|
* Support building using an external toolchain. Questions to the mailing list ↵"Steven J. Hill"2007-02-061-61/+14
| | | | and all other comments to <biteme@devnull.com>.
* - reformat help text to fit default width betterBernhard Reutner-Fischer2007-01-241-6/+11
|
* - remove old reminder that is already dealt with.Bernhard Reutner-Fischer2007-01-211-10/+0
|
* Add support for mklibs (strips unused syms from shared libs such as uClibc)Eric Andersen2006-08-021-0/+1
| | | | | based on a patch from akvadrako, and using a version of mklibs.py that was massively hacked up by andersee and mjn3 for uClibc support.
* disable multilib by defaultMike Frysinger2006-02-201-1/+1
|
* initial attempt at adding elf2flt support based upon marcs work in Bug 273Mike Frysinger2006-01-101-2/+3
|
* touchup descriptionsMike Frysinger2005-08-091-1/+1
|
* Sigh... Let's try this again.Manuel Novoa III2005-08-041-1/+1
|
* Add BR2_CROSS_TOOLCHAIN_TARGET_UTILS to allow bundling of some useful debugManuel Novoa III2005-08-041-0/+11
| | | | | apps with a deployed cross toolchain. Should probably do ltrace as well... Also, add another compat symlink for cross gdb.
* Add sstrip for host and/or target.Manuel Novoa III2005-08-031-0/+1
|
* Someone forgot mipsel for soft float...Manuel Novoa III2005-04-301-1/+1
|
* Patch from acmay: http://bugs.uclibc.org/view.php?id=47Eric Andersen2005-01-231-1/+1
| | | | | | | | | | 0000047: ARM BigEndian does not allow Soft Float When ARMEB is selected for the arch I am unable to select soft float support. The toolchain/Config.in does not have a depend for armeb, it just has arm. The attached patch should cover it.
* Fixup SOFT_FLOAT handlingEric Andersen2004-10-091-5/+0
|
* allow people to enter target optimizationsMike Frysinger2004-10-091-3/+2
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-04 00:13:28 +0000