busybox-w32/scripts, branch dscho-kill-gently

Merge branch 'busybox' into merge

2017-08-22T13:56:12+00:00

klibc-utils: new applets: resume, nuke, minips

2017-08-18T17:15:29+00:00

minips is a pure alias to ps, just in case someone needs 100% klibc-utils compat. nuke is a primitive version of "rm -rf" without options and error checks. ~30 bytes. resume is a tool for initramfs which resumes from a given block device. function old new delta resume_main - 582 +582 packed_usage 31640 31712 +72 nuke_main - 28 +28 xstrtoull - 24 +24 applet_names 2646 2665 +19 applet_main 1532 1544 +12 applet_suid 96 97 +1 applet_install_loc 192 193 +1 applet_flags 96 97 +1 ------------------------------------------------------------------------------ (add/remove: 5/0 grow/shrink: 6/0 up/down: 740/0) Total: 740 bytes Signed-off-by: Denys Vlasenko

do not use `a' quoting style in comments

2017-08-02T12:26:33+00:00

Signed-off-by: Denys Vlasenko

Merge branch 'busybox' into merge

2017-07-24T11:03:28+00:00

crond: do not assume setenv() does not leak

2017-07-22T00:25:47+00:00

Signed-off-by: Denys Vlasenko

Merge branch 'busybox' into merge

2017-07-18T14:58:52+00:00

build system: FEATURE_LIBBUSYBOX_STATIC - try to pull libc/libm into libbusybox

2017-07-15T12:52:26+00:00

It variously fails with different toolchains I tried... Signed-off-by: Denys Vlasenko

kbuild: avoid warning when building with KBUILD_NO_NLS

2017-07-14T14:14:37+00:00

The return values of bindtextdomain() and textdomain() are not actually used at all... Signed-off-by: Johannes Schindelin

kbuild: simulate force-renaming on Windows

2017-07-14T14:14:37+00:00

Calling rename() when a file with the target name exists already fails on Windows. Let's simply delete the target file, if it exists. This is usually a dangerous thing as it leaves time between deleting and renaming, during which (theoretically) another thread or process could have created the same file, and the rename() would fail again. Practically, we are talking about the kbuild system used to configure the build, where it does not matter, as we do not expect any other thread or process to interfere with the configuration files. Signed-off-by: Johannes Schindelin

kbuild: support at least non-interactive mode on Windows

2017-07-14T14:14:30+00:00

without POSIX, kbuild has some trouble compiling its support executables. Luckily, the parts that really lean on POSIX functionality are pretty much all only needed when configuring the build interactively. When compiling BusyBox for Win32, we do not actually need interactive configuration at all: we simply choose the default. Therefore, a lot of the stuff that is typically built for the Kconfig system is totally unnecessary (such as: compiling documentation via fork()&exec(), changing the window size, etc). Liberally put all of the problematic code behind #ifndef __MINGW32__ guards, just to get `make mingw64_defconfig` going in Git for Windows' SDK (which is a special-purpose version of MSYS2). Signed-off-by: Johannes Schindelin