| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
See https://bugs.busybox.net/show_bug.cgi?id=15931 for details of the
fix not yet upstreamed.
|
|
|
|
... so that we can install-with-deps the wrapper, in case the bootstrap
compiler has dependencies not present on the host machine.
|
|
|
|
|
|
Unfortunately, this does not entirely removes the requirement of
a /bin/sh being present, as awk(1) is invoked during the build to
use popen(3) in one place, a libc function that has a hard-coded
reference to /bin/sh. Nevertheless, using our interpreter wherever
possible greatly reduces the dependency on the host system.
|
|
... in a way that is supported by configure scripts without
any guessing.
|
|
... instead of relying on hard-coded /bin/sh in the #!-line.
Also add our interpreter in scripts that are called directly
during the build.
|
|
... instead of relying on the #!-line that hard-codes /bin/sh.
|
|
In stage 0, bootstrap a pretty complete tool collection, so that
we can bring ourselves the tools needed by the configure scripts
of the early stages.
|
|
|
|
... as it was only needed by plugin-api.h, which is not
included anymore since plugins have been disabled.
|
|
... to avoid linking libdl.
|
|
|
|
|
|
... and drop rule-injected LDFLAGS for all bootstrap targets
in stage-0, as those flags might not be supported by the
unknown bootstrap compiler.
|
|
|
|
|
