summaryrefslogtreecommitdiff
path: root/scripts/build
AgeCommit message (Collapse)AuthorFilesLines
2015-12-08Whitespace: We don't use tabs in shell or kconfig filesBryan Hundven4-35/+35
We indent by multiples of 4. This change cleans up whitespace in offending files. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-12-08scripts: Update usage of CT_GetCustomBryan Hundven9-89/+29
This commit updates the build scripts to match the new usage of CT_GetCustom from the previous change. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-12-08Linux: Remove obsolete Linux custom headersBryan Hundven1-47/+3
This option allowed you to use a custom headers directory/tarball to use in your sysroot. Not to be confused with using a custom source, that option is the preferred method. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
2015-12-08xtensa: Remove support for CT_CUSTOM_LOCATION_ROOT_DIRBryan Hundven1-7/+1
Since CUSTOM_LOCATION_ROOT_DIR was removed from config/global/paths.in in commit c499ccb, xtensa should depend only on it's ARCH_XTENSA_CUSTOM_OVERLAY_LOCATION. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
2015-12-08Merge pull request #282 from bhundven/less_gcc_versions_part2Bryan Hundven3-239/+32
Less gcc versions part2
2015-12-07binutils: Fix LDFLAGS for static toolchainBryan Hundven1-1/+1
If building a static toolchain, the ldflags option passed to do_binutils_backend is overridden when we set `LDFLAGS=-all-static`. We should pass `LDFLAGS=${ldflags} -all-static` in this case. This fixes #297 Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-12-05binutils: Fix binutils manuals_install variableBryan Hundven1-2/+2
In commit: 74d555b2 A regex in a parameter subsitution replaces a '#' hash symbol, but it is not made literal '\#', so from the hash to the end of the line is a comment. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-30gcc: Gnu OpenMP support depends on threadingBryan Hundven1-1/+0
Instead of checking if thread support is enabled during the build, move the check to kconfig-time. Since if threading support is not availble, libgomp should not be available either. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-30gcc: CLooG should be optional for configureBryan Hundven1-2/+6
Because >= gcc-5.x does not require cloog, it should not be forced on the command line arguments for configure if graphite is enabled. Make CLooG optionally added, if it is needed (aka: <= gcc-4.9). Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-30PPL: Remove support for PPL and CLooG/PPLBryan Hundven3-216/+21
Now that versions of gcc that required PPL are no longer supported ( >= gcc-4.5.x AND <= gcc-4.7.x ) ...we no longer require PPL or CLooG/PPL. This commit: * Removes PPL * Removes CLooG/PPL * Updates the documentation * Updates build script for CLooG and GCC * Removes PPL and CLooG/PPL from scripts/addToolVersion.sh and scripts/showSamples.sh * Adds ISL to scripts/addToolVersion.sh and scripts/showSamples.sh I know that sounds like a lot for one commit, but it was all kind of inter-tangled. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-30gcc: Remove gcc <= 4.7.xBryan Hundven1-21/+6
As per #222, in crosstool-NG >= 1.23.0, we will only support: [upstream supported gcc versions] - 1 As of this writing, these versions are: * 5.2.0 * 4.9.3 * 4.8.5 (the -1, since development on 4.8.x is now closed) I plan to keep 4.8.5 around because of some architectures having issues with over-optimization or just faulty optimization in the 4.9.x and possibly newer versions. I also cleaned up a requirement for glibc to depend on >= gcc-4.6.x for >= glibc-2.20, but since the lowest gcc we support after this change is >= 4.8.5, this condition can go away. Patches for older gcc versions are removed in the next commit. This closes #222 Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-25binutils/gdb: Fix configure options when building from binutils-gdb repoBryan Hundven2-0/+19
When building from: {git,http}://sourceware.org/git/binutils-gdb.git and setting BINUTILS_CUSTOM or GDB_CUSTOM, they could be the same source. These config options should not affect normal released versions. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-23uClibc: Add kconfig option to enable IPv6 supportBryan Hundven1-0/+7
This commit adds a kconfig option to enable IPv6 support. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-22Clang: Use {C,CXX}FLAG -fbracket-depth=512 for GCC buildRay Donnelly1-0/+13
https://llvm.org/bugs/show_bug.cgi?id=19650 https://gcc.gnu.org/ml/gcc/2014-05/msg00014.html Signed-off-by: Ray Donnelly <mingw.android@gmail.com>
2015-11-21uClibc: remove references to sh64*Bryan Hundven1-1/+0
As per the change notes of GCC-6: https://gcc.gnu.org/gcc-6/changes.html and conversations I've had with the buildroot folks, there is no need to support sh5/sh64. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-17Merge pull request #268 from bhundven/consistent_usage_of_found_appsBryan Hundven33-173/+173
consistency: Use exported variables of required tools
2015-11-17consistency: Use exported variables of required toolsBryan Hundven33-173/+173
We check for apps: * make * sed * grep * awk * libtool/libtoolize * install * patch * and more ...during configure. Our scripts should be consistent about using the variables that define where the found tool was found. Of course, we do hard-link these tools in buildtools, but that should be a backup for the components we are building. Our scripts should always use the tools we find. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-16ncurses: bump to ncurses-6.0Bryan Hundven1-0/+4
This commit removes ncurses-5.9 and adds 6.0. I also provide the stable patch updates in patches/ncurses/6.0. I have also added an experimental toggle for enabling the new ABI support. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-15file modes: Fix file modes... again.Bryan Hundven3-0/+0
These files are sourced, not executed, and do not need to be executable. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-13Update new companion libs with *_for_target.Alexey Neyman2-0/+2
Signed-off-by: Alexey Neyman <stilor@att.net>
2015-11-13Pass CFLAGS/LDFLAGS to backends.Alexey Neyman2-1/+11
Signed-off-by: Alexey Neyman <stilor@att.net>
2015-11-13Clean up 300-gdb.sh a bit.Alexey Neyman1-52/+31
Now that expat/curses have migrated into separate script, no need for do_debug_gdb_parts() and need_gdb_src checks. Signed-off-by: Alexey Neyman <stilor@att.net>
2015-11-13Enable building expat/ncurses for host.Alexey Neyman3-2/+54
Then re-enable cross-gdb for nios2-spico-elf sample, previously disabled.
2015-11-13Change ncurses to a companion library.Alexey Neyman2-112/+110
Currently, builds for build and target (matching the current implementation). Need to add building for host for canadian crosses. TIC_PATH is removed - configure in ncurses searches $PATH, so it finds 'tic' in buildtools anyway. Arguably unneeded code for MacOS also removed, with a FIXME comment for validation by someone using MacOS. Signed-off-by: Alexey Neyman <stilor@att.net>
2015-11-13Convert expat for target into a companion lib.Alexey Neyman2-53/+67
Expat-for-host to be done. Signed-off-by: Alexey Neyman <stilor@att.net>
2015-11-13Build companion libs for target.Alexey Neyman7-3/+16
Currently, only libelf has a for-target step - but it generalizes the step to hook other libraries into this step. Signed-off-by: Alexey Neyman <stilor@att.net>
2015-11-13xtensa: add support for the configurable Xtensa architecture.Chris Zankel5-0/+99
The Xtensa processor architecture is a configurable, extensible, and synthesizable 32-bit RISC processor core. Processor and SOC vendors can select from various processor options and even create customized instructions in addition to a base ISA to tailor the processor for a particular application. Because of the configurability, the build process requires one additional step for gcc, binutils, and gdb to update the default configuration. These configurations are packed into an 'overlay' tar image, and are simply untarred on top of the default configuration during the build. Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
2015-11-13Merge pull request #239 from diorcety-ctng/cc-cygwin-mingw-linuxBryan Hundven4-1/+264
Canadian cross build = x86_64 Cygwin host = x86_64 MinGW_W64 target = x86_64 GNU/Linux
2015-11-13Merge pull request #245 from villytiger/install-stripBryan Hundven2-2/+6
Use install-strip target for gcc optionally
2015-11-13Merge pull request #221 from bhundven/uclibc-ngBryan Hundven1-238/+199
Add support for uClibc-ng
2015-11-13libtool: Update to 2.4.6 and patch for CygwinRay Donnelly1-1/+1
Signed-off-by: Ray Donnelly <mingw.android@gmail.com>
2015-11-13Add gettext and libiconv as companion libsRay Donnelly3-0/+263
.. they're needed for the RPC generation in glibc on both Cygwin and MinGW-w64. Neither are built on GNU/Linux and iconv is not built on Darwin. Two patches for gettext are needed, one so that -O0 works and one so that static builds can be made. They can take a good while to build, so if not needed for_host or for_build then they are not built. Signed-off-by: Ray Donnelly <mingw.android@gmail.com>
2015-11-13uClibc: Fall back to default configs if not providedBryan Hundven1-1/+4
I've added the .config files to contrib/uClibc-defconfigs from buildroot to use as default configs if they are not provided in the sample. If a particular architecture really needs an option set, it should be either updated in the manange_uClibc_config function in scripts/build/libc/uClibc.sh or a custom ${uclibc_name}.config should be added to the sample (usually via `ct-ng saveconfig`). Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-13uClibc: Add support for uClibc-ngBryan Hundven1-10/+17
This commit adds uClibc-ng 1.0.8. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-13uClibc: rewrite mungeuClibcConfig to manage_uClibc_configBryan Hundven1-219/+177
This commit updates uClibc to use the new CT_Kconfig options from the previous commit. The older sed method of sanity checking the uClibc .config was error prone and clumsy. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-12mpfr: Swap primary mirror to gnu.orgBryan Hundven1-2/+2
mpfr.org has been less then reliable, so lets make gnu.org the primary instead of the secondary source. This closes #250 Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-11uClibc: Reduce supported versionsBryan Hundven1-8/+1
This commit reduces the number of supported versions to: * 0.9.33.2 * custom location Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-11Use install-strip target for gcc optionallyIlya Lyubimov2-2/+6
2015-11-11Disable parallel build of mingw-w64-crt.Alexey Neyman1-1/+4
Unfortunately, parallel build issue is not yet fixed in current mingw-w64 sources. Signed-off-by: Alexey Neyman <stilor@att.net>
2015-11-10blackfin: Remove blackfin supportBryan Hundven3-18/+2
This commit removes blackfin support. I'm open to re-adding blackfin after crosstool-1.23.0 is released, but it is currently too difficult to port forward to newer versions of gcc and uclibc. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-03uClibc: Don't use CROSS, use CROSS_COMPILE insteadBryan Hundven1-9/+9
As per: http://cgit.uclibc-ng.org/cgi/cgit/uclibc-ng.git/commit/Makefile.help?id=044843f002f666db3bc06c513ed6291a00ad1225 CROSS= is for compatibility, but we plan on dropping older uClibc versions, and adding uClibc-ng and uClibc-snapshot support. Use CROSS_COMPILE instead. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-11-03linux: Set CROSS_COMPILE while building/checking headersBryan Hundven1-0/+2
Some architectures, like arc and blackfin set CROSS_COMPILE to a default if it is not set on the command-line. Since we are building the cross-compiler, we need to ALWAYS set CROSS_COMPILE, since building/checking headers is done after the GCC PASS1 step. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-10-31gcc: Support only the latest branch releases of gccBryan Hundven2-32/+0
This change, as per #222, reduces the number of supported releases of gcc to the latest branch releases. I noticed while doing this work that gcc-4.5.4 was never added, so I moved patches for gcc-4.5.3 to 4.5.4 and updated the bfin-unknown-linux-uclibc example. Also, 120-siginfo.patch was fixed upstream in the 4.5.4 release, so this patch is omitted. I also bumped the avr sample to 4.9.3 from 4.9.2. With the addition of gcc-5.x, the gcc release team now releases the major.minor.0 versions, while updates to the branch are available in svn/git. We'll address that when we get to issue #219. This change just removes CC_GCC_5_1 and moves CC_GCC_5_2 to CC_GCC_5, and removes CC_GCC_5_1_or_later and moves CC_GCC_5_2_or_later to CC_GCC_5_or_later. This is the first of two part changes, as mentioned in #222. This change is slated for release in 1.22.0. The next change will be slated for 1.23.0, and will limit gcc versions to what is on https://gcc.gnu.org under "Release Series and Status", which is currently 4.9.3 and 5.2.0, although I will also support the previous supported version. In this example that would be 4.8.5. Last, but not least, this change also retires AVR32 support. Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
2015-10-27Clean up *.la after installing compiler/libraries.Alexey Neyman1-0/+19
Having *.la in the installation directory breaks ltrace: in ltrace, libtool somehow considers libsupc++ to be an "accessory library" and does not add -lsupc++ to the link flags. Neither Ubuntu, nor RedHat include *.la files into their packages for libstdc++. Signed-off-by: Alexey Neyman <stilor@att.net>
2015-10-09Using "all" and "install" targets in do_gcc_core_backend if configured.Jasmin Jessich1-9/+47
- New configurations: - CC_GCC_TARGET_FINAL: Use the default targets "all" and "install" for the final compiler for bare metal. - Adding parameter "build_step" to function do_gcc_core_backend: do_gcc_core_backend is used for the core compiler and in case of bare metal for the final compiler, too. To have better control over the parameters for the final compiler "build_step" is used. - Used for proper logging. - Use CT_CC_GCC_CORE_EXTRA_CONFIG_ARRAY or CT_CC_GCC_EXTRA_CONFIG_ARRAY. - If CT_CC_GCC_TARGET_FINAL is set and the final compiler is build then the make targets for the final compiler are used ("all", "install"). Signed-off-by: Jasmin Jessich <jasmin@anw.at>
2015-10-07Merge pull request #187 from jasmin-j/sync_ltoBryan Hundven1-0/+2
Synchronize CC_GCC_USE_LTO parameter setting II
2015-10-07Merge pull request #184 from jasmin-j/add_gcc_env_arrayBryan Hundven1-2/+7
Add additional environment variables for gcc build.
2015-10-07Merge pull request #182 from jasmin-j/add_missing_lib_optsBryan Hundven1-0/+15
Adding missing if/else blocks in do_gcc_core_backend.
2015-09-24Synchronize CT_CC_GCC_USE_LTO parameter setting in do_gcc_backend with the oneJasmin Jessich1-0/+2
from do_gcc_core_backend, by adding "--enable-lto"/"--disable-lto". Signed-off-by: Jasmin Jessich <jasmin@anw.
2015-09-21Added additional environment variables for gcc build (make) with new optionJasmin Jessich1-2/+7
GCC_EXTRA_ENV_ARRAY. Signed-off-by: Jasmin Jessich <jasmin@anw.at>
generated by cgit v0.10.2-6-g49f6 at 2024-05-04 01:52:46 (GMT)