diff options
| author | Klaus Aehlig <klaus.aehlig@huawei.com> | 2024-12-19 13:22:37 +0100 |
|---|---|---|
| committer | Klaus Aehlig <klaus.aehlig@huawei.com> | 2024-12-19 17:38:14 +0100 |
| commit | 2c1e0733981fc3fc7531530f13f56e9c28d457f5 (patch) | |
| tree | a832ac556419d675f49388b7c297d16a0c6524a0 /README.md | |
| parent | b727fce66b3601bddf4f37d64a620caba5e8a786 (diff) | |
| download | bootstrappable-toolchain-2c1e0733981fc3fc7531530f13f56e9c28d457f5.tar.gz | |
Support wrapping bootstrap CC for autotools
During the initial bootstrap phase, an old autotools project (gcc
4.7.4) is built and this potentially with a new compiler. For some
of the tests carried out by the autotools, the compiler is used
without the CFLAGS provided. Therefore, offer to wrap the compiler
with the given flags to avoid that the autotools draw incorrect
conclusions if the compile attempt fails for a different reason,
e.g., because implicit declarations are now considered errors by
default by modern C compilers.
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -171,6 +171,11 @@ Fields for building the toolchains: Library directory of the C library on the build host (default: not set) - `HOST_DYNAMIC_LINKER`: Absolute path to the dynamic linker on the build host (default: not set) +- `BOOTSTRAP_WRAP_CC`: + If true, when using the bootstrap C compiler with autotools, use a wrapper + script calling the compiler with the `BOOTSTRAP_CFLAGS` instead. In this way, + it can be avoided that the autotools draw wrong conclusions from calling the + compiler without the specified flags (as some tests do). - `INCLUDE_LINTER`: Add linter to toolchain if supported, e.g., `clang-tidy` (default: `false`) |