Initialize ret to 0 so compiler no longer complains about
monitor.c: In function 'lxc_monitor_open':
monitor.c:212:5: error: 'ret' may be used uninitialized in this function [-Werror=maybe-uninitialized]
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Per default, vim creates a new file and keeps the original file as backup.
This leads to crontab checking the backup file for changes instead of the
one actually being edited, resulting in any changes being silently dropped.
Since busybox's crontab saves temporary crontab files in "/etc/crontabs.*"
vim's default of "backupskip=/tmp/*" doesn't circumvent this.
This commit fixes this issue by appending "/etc/crontabs.*" to "backupskip".
Signed-off-by: Florian Fieber <florian@florianfieber.de>
seccomp was unconditionally disabled before.
Also a non-escaped newline in a place where it should be escaped
made the build process skip some CONFIGURE_ARGS.
Fix CONFIGURE_ARGS and add an option to allow building with seccomp.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
- Add patch to get WEXITSTATUS and WIFEXITED defined
The issue is fixed in upstream's development repo, so the patch won't be
needed with ncdu's next release.
- Depend on more commonly used libncurses instead of libncursesw
- Enable parallel build
- Update copyright
Signed-off-by: Charles Lehner <cel@celehner.com>
stdin, stderr and stdout are constants on musl and it doesn't provide
mallinfo.
Both, overwriting std* were used to catch and work around various
misbehaviours of glibc, so it's hopefully save to just skip them when
building against other libc implementations.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
- update to latest version (v5.2.1)
- add license info
- add myself as maintainer
- put everything in a "Compression" submenu
- reduce the number of packages (put symlinks with their matching target)
Signed-off-by: Nicolas Thill <nico@openwrt.org>
gatttool is not included in `make install`. The Debian package
similarly copies it out of the build directory.
Signed-off-by: Kevin Mehall <km@kevinmehall.net>
The previous commit
ba4338d mmc-utils: don't set -D_FORTIFY_SOURCE in Makefile
applied the global value of FORITFY_SOURCE also to mmc-utils.
As the package was meant to be built with FORTIFY_SOURCE upstream,
restore that behaviour and make it play nice with the global setting
by undefining the macro before defining it.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>