Age | Commit message (Collapse) | Author |
|
... and drop unneeded duplication as well as wrong expansion
variables in "PATH" fields.
|
|
... as that is brought in by the shell toolchain anyway. In that
way, we can also drop setting "PATH" and hence get rid of the
assumption that variable-expansion happens in "PATH" strings.
|
|
The "PATH" field in ["CC", "defaults"] is taken literally (currently
outside the foreign rules, in the future everywhere), so a reference
to the toolchain does not work. However, it is not necessary either,
so simply drop it.
|
|
... and not only the bootstrap one. For tests, it is useful to
have tools like realpath(1) and date(1) that are not needed for
bootstrapping.
|
|
... and also add the missing bindings for the remaining test rules.
|
|
|
|
|
|
|
|
... using the full busybox from stage-0
|
|
... thus having less requirements on our bootstrapped shell tool chain.
|
|
|
|
|
|
|
|
... to propagate foreign tools that are the same in each
rule set (e.g., busybox, make).
|
|
... as those rules are only used by tools.
|
|
... and drop rule-injected LDFLAGS for all bootstrap targets
in stage-0, as those flags might not be supported by the
unknown bootstrap compiler.
|
|
|