summaryrefslogtreecommitdiff
path: root/strata/build-essential/gcc.morph
Commit message (Collapse)AuthorAgeFilesLines
* Remove all .morph files and files from the old formatJavier Jardón2017-12-121-62/+0
|
* gcc: Remove 'with-cpu', not compatible with 'with-arch'Pedro Alvarez2016-06-021-1/+0
| | | | | | | | | | | | | | The following error was happening after upgrading to GCC 5.3.0 in armv7lhf builds: Switch "--with-arch" may not be used with switch "--with-cpu" Also, I could find other places where this flag was removed when upgrading to GCC 5: http://pkgs.fedoraproject.org/cgit/rpms/gcc.git/commit/gcc.spec?id=7f999936529d6902d43c8cc807ceb3a6843f3072 Change-Id: Ib3934098518dc496d3c9d29a9c7f97a7cfeab9c7
* Reformat all definitions according to a consistent styleSam Thursfield2015-07-191-4/+3
| | | | | | | | | | | | | | | | | This was done using the 'indent' tool, which uses a fork of PyYAML named 'ruamel.yaml' to rewrite YAML files without losing comments, ordering, or certain elements of formatting. My aim with doing this is to open the door to automated editing of the reference system definitions using the 'ruamel.yaml' library. This can be used to implement automated migration when we want to make changes to the YAML format that we use to represent Baserock system definitions. Although this looks drastic, remember that it's actually only altered 65 out of 608 .morph files -- the vast majority already pass unchanged through my version of ruamel.yaml. Change-Id: I95ec978714b5bd1c02c90183336a9fbb846cb692
* gcc: set correct host/target for GMP for armv5Javier Jardón2015-04-281-0/+2
| | | | Change-Id: I8220cd76e947de26335066357d69d2c5c204257c
* gcc.morph: Define splitting rulesRichard Maw2015-02-251-0/+16
|
* Embed morph-arch and morph-arch-configbaserock/tiagogomes/update-toolchain-v2Paul Sherwood2015-01-231-1/+10
| | | | This will make it easier to advance refs later.
* Update GCC to 4.9.2Tiago Gomes2015-01-231-18/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Update the GCC compiler to the 4.9.2 version. It turns out that a C++ compiler is required to build the latest GCC releases, so build one in stages 1 and 2 as well. The updated list of GCC configuration options that either don't work in a cross compiler or are not needed in a temporary compiler, were based on the latest instructions from Linux From Scratch. The inclusion of /lib64 in the lib path for the stage 1 linker is an attempt to turn things more robust rather than to just symlink in /lib stuff that ends up installed in /lib64 (as it is already being done for libgcc_s.so). Ideally, we should configure every chunk to install to /lib, however GCC seems to not honour the `--with-libdir` configuration flag. With this version of GCC, it looks like a sysroot needs to be given at configure time so that `--with-native-system-header-dir` does what it claims to do. Unfortunately, this has the side effect of making GCC not passing to the linker the linker sysroot flag: `-Wl,--sysroot=$SYSROOT`. The workaround is to modify LDFLAGS to give a sysroot directly to GCC, `--sysroot=$SYSROOT`, which will then be further passed down to the linker. As the newest version of GCC finds more warnings than the previous one, `-Werror` was disabled for the coreutils, GDB and Syslinux projects. Syslinux's Makefile had to be patched, as it is not possible to disable `-Werror` for all targets through the NO_WERROR variable. The hack to handle libgcc_eh being required during eglibc's build was removed, as it doesn't seem to be the case anymore.
* Improve the readability and docs of gcc morphologiesTiago Gomes2015-01-221-19/+21
| | | | | No functional changes here. It will ease the review of the following commmits.
* Add back missing comments to build-essential chunk morphsSam Thursfield2014-09-261-1/+15
| | | | | These will have been lost in the automated chunks-in-definitions transition.
* Re-organise definitions with scripts/organise-morphologies.pyGENIVI-I0.1baserock/release/GENIVI-I0.1Richard Maw2014-08-181-0/+28