diff options
| author | Oliver Reiche <oliver.reiche@huawei.com> | 2024-01-10 12:09:51 +0100 |
|---|---|---|
| committer | Oliver Reiche <oliver.reiche@huawei.com> | 2024-01-10 13:18:55 +0100 |
| commit | 19faf1fa1f5aff4854377824e6d4a8b9c0c09032 (patch) | |
| tree | 043593c27498473e133795295cdb62bac17121f9 /README.md | |
| parent | 816d0f68b162ec7096442a60d6f818ae45383e76 (diff) | |
| download | bootstrappable-toolchain-19faf1fa1f5aff4854377824e6d4a8b9c0c09032.tar.gz | |
Introduce and honor BOOTSTRAP_CFLAGS
... and drop rule-injected LDFLAGS for all bootstrap targets
in stage-0, as those flags might not be supported by the
unknown bootstrap compiler.
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 10 |
1 files changed, 6 insertions, 4 deletions
@@ -119,10 +119,10 @@ For bootstrapping the toolchains, the build host must be a Linux system with: 3. C compiler (e.g., TinyCC, old GCC) The C compiler for bootstrapping can be specified by setting the fields -`BOOTSTRAP_CC` and `BOOTSTRAP_PATH` in configuration variable `TOOLCHAIN_CONFIG` -(e.g., on command line `-D'{"TOOLCHAIN_CONFIG": {"BOOTSTRAP_CC": "gcc"}}'`). If -not set, the C compiler is assumed to be `cc` available in the search paths -`/bin` or `/usr/bin`. +`BOOTSTRAP_CC`, `BOOTSTRAP_CFLAGS`, and `BOOTSTRAP_PATH` in configuration +variable `TOOLCHAIN_CONFIG` (e.g., on command line `-D'{"TOOLCHAIN_CONFIG": +{"BOOTSTRAP_CC": "gcc"}}'`). If not set, the C compiler is assumed to be `cc` +available in the search paths `/bin` or `/usr/bin`. *Note that currently supported build hosts are required to be an `x86_64` architecture and use either the GNU or musl C library.* @@ -158,6 +158,8 @@ Fields for building the toolchains: - `BOOTSTRAP_CC`: The initial C compiler for bootstrapping (default: `"cc"`) +- `BOOTSTRAP_CFLAGS`: + The initial C compile flags for bootstrapping (default: `["-w"]`) - `BOOTSTRAP_PATH`: Search path for the initial C compiler (default: `["/bin", "/usr/bin"]`) - `HOST_SYSTEM_HDR_DIR`: |