summaryrefslogtreecommitdiff
path: root/build-essential.morph.yaml
Commit message (Collapse)AuthorAgeFilesLines
* Replace JSON morphologies with YAML.Richard Maw2013-07-021-287/+0
|
*-. Merge remote-tracking branches 'origin/samthursfield/comment-fix' and ↵Richard Maw2013-05-281-31/+7
|\ \ | | | | | | | | | | | | | | | 'origin/baserock/richardmaw/inspect-zlib' Reviewed-by: Daniel Silverstone, briefly in person.
| | * build-essential: remove stage2-zlibRichard Maw2013-05-241-22/+0
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The stage 1 toolchain is built with --disable-shared, which means it is unable to build shared libraries. This causes it to include symbols from libgcc in the zlib shared object. This causes problems in pass 3, since by then we have a toolchain that is suitable for building shared objects, so it doesn't include libgcc symbols in zlib. This causes problems while building gcc, since cc1 is compiled against the zlib in /tools, but is run with the zlib in /usr, so it fails to run due to missing symbols, which would otherwise come from libgcc_s or be copiled in as part of libgcc.a. stage 2 zlib was originally added to avoid gcc and binutils needing to use their embedded copy, which would improve compile speed slightly and the other reasons to prefer shared objects. However, the bootstrap is fragile enough without it, it may be the case that gcc and binutils prefer to embed zlib for precisely these reasons.
| * Fix comment in build-essential.morph.yamlSam Thursfield2013-05-231-9/+7
|/
* Fix up refs after mergeSam Thursfield2013-03-151-21/+21
| | | | I'm not sure how these got lost.
* Add zlib to build-essentialSam Thursfield2013-03-141-1/+42
| | | | | | It's never good to have multiple versions of the same library in use on a system, so we should avoid using the versions of ZLib that are bundled in the GCC and Binutils releases.
* Add new build-essential morphologySam Thursfield2013-03-141-0/+270