| Age | Commit message (Collapse) | Author |
|---|
|
genbuild() is a bunch of echo statements, and with enough parallelism piping
its output to "head" can close the pipe before all the echo statements have
run, then they complain about writing to a closed pipe. (We're intentionally
discarding the output, it's not an error, so...)
|
|
|
|
changed), better error message when .config missing.
|
|
(Output file is read only because broken installs that write to the old filename
will truncate+overwrite toybox binary otherwise.)
|
|
xparsetime() not to need floating point, adjust callers.
|
|
|
|
glibc doesn't have _XOPEN_UUCP (though bionic does), which meant that the
generated array of values was out of sync with the hand-written array of
names.
This patch removes that by using a unified array and the preprocessor.
A side benefit of this for me is that it makes toybox easier to integrate
in the AOSP build system (the less shell script magic, the better).
|
|
build context (probes for portability.h) is too fiddly to keep stright,
just copy the parts we need into the host tool.
|
|
|
|
(see comment in ulimit.c about the glibc header bug), so copy prototype into
the probe too. Without this ulimit always disabled by config probe.
|
|
|
|
then install bison and flex. (Not yacc and lex, the kernel build is calling
the propreitary versions.)
|
|
This is useful e.g. for cross toolchains that define $CC and $STRIP
instead of $CROSS_COMPILE.
|
|
|
|
If you ever do have a command name beginning with a -, eval won't run it by
default, because even though it takes no arguments it tries to parse them
anyway, so it complains it's an unrecognized argument. Solution: -- as first
argument (which is parsed and stops argument parsing).
|
|
|
|
|
|
wouldn't let him assign a negative default value, so I fixed it.
|
|
|
|
|
|
in segfaults on newer toolchains. (That entire section is due for a rewrite.)
|
|
The GITHASH problem was building a tarball version under an existing git repo,
where git describe found ../../../../.git so only call git if we have a .git
directory in the source.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
https://landley.net/notes-2013.html#28-03-2013 so add it to the airlock install.
|
|
check in two converted commands.
|
|
and make uptime use it.
|
|
|
|
|
|
(instead of just producing no output on stdout like everybody else).
|
|
|
|
|
|
So use $SED to indicate the sed to use, and set it to 'gsed' if available.
|
|
(This made ls -l not work when LS_COLOR was off.)
|
|
The problem is that .config and .singleconfig produce the same header file,
so checking that the header is newer than the .config file won't help if
it was last generated from the other file.
|
|
function, and add $C variable with an absolute path to the command being tested
(you need to call things like printf by path to avoid shell builtins, might as
well be consistent).
|
|
headers during install to make other install targets robust against single
command builds between "make" and "make install" of multiplexer version.
|
|
but not nsenter(). So probe for both.
|
|
last test exited with nonzero status and the script preserved it. In the
current context, that's counterproductive.
|
|
command was trying to parse their options and failing. (Commands
that aren't just disabled but have no option string even in the allyesconfig
case need an OPTSTR of 0.)
This is probably only a partial fix, there's some design work to think through
here.
|
|
a patch from Elliott Hughes, who said:
[PATCH] Add support for libcrypto for MD5/SHA.
Orders of magnitude faster (for architectures where OpenSSL/BoringSSL
has optimized assembler).
Also adds sha224sum, sha256sum, sha384sum, and sha512sum for folks
building with libcrypto.
The fallback portable C implementations could easily be refactored
to be API-compatible, but I don't know whether they'd stay here or
move to lib/ so I've left that part alone for now.
|
|
resulting macro.)
|
|
In main.c: used adjusted string with placeholers for removed options (so flag
values don't move based on config, allowing FORCE_FLAGS to work).
In scripts/mkflags.c: test was wrong, a bare longopt never matches a single
letter command, but it was treated as always matching when comparing
allyesconfig vs current config to determine which options were disabled, so
there was a corner case that got the flag values wrong.
|
|
|
|
Unstable sorting means confusing diffs if you're checking in the generated
files. (Which I shouldn't be doing, but getting this bundle of random scripts
into Android's build system isn't going to be easy...)
|
