Mathias Kresin [Tue, 24 May 2016 19:30:40 +0000 (21:30 +0200)]
ddns-scripts: add support for glue records
Assuming the following dns zone configuration for kresin.me:
. 1800 IN NS ns.inwx.de.
home.kresin.me. 1800 IN NS gw.home.kresin.me.
gw.home.kresin.me. 60 IN A 198.51.100.1
Using the example, gw.home.kresin.me is a glue record and used as DDNS
record as well. gw.home.kresin.me points to the OpenWrt installation
where the ddns-scripts are running.
Since ns.inwx.de isn't the authoritative server for home.kresin.me,
a query for the the A record of gw.home.kresin.me will be "forwarded"
to and replied by the authoritative server 198.51.100.1. If the
authoritative server can't be reached, the query times out without any
address returned.
The only way to get the A record of the glue record is to use bind
host in verbose output mode, query ns.inwx.de for gw.home.kresin.me and
evaluate the additional section of the response.
To my knowledge, only bind host in verbose output mode shows the
additional section of the response. Therefore, this features depends on
bind host.
It is not possible to use the bind host verbose mode for all queries.
In verbose mode the "has address" line isn't returned. Grepping for the
hostname might fail if the hostname is CNAME. Grepping for the first
occurrence of an ip-address is way to error prone, since it could
return the ip address of a different record type.
Jo-Philipp Wich [Mon, 30 May 2016 17:11:37 +0000 (19:11 +0200)]
crtmpserver: fix multiple issues
- Switch download to the Github clone of crtmpserver
- Rebase patches against latest version
- Pregenerate version.h file
- Disable applestreamingclient as it is broken
John Crispin [Mon, 30 May 2016 16:34:08 +0000 (18:34 +0200)]
krb5: more uninitialized warning errors
ktutil_funcs.c: In function 'ktutil_delete':
ktutil_funcs.c:75:28: error: 'prev' may be used uninitialized in this function [-Werror=maybe-uninitialized]
Jo-Philipp Wich [Mon, 30 May 2016 12:27:54 +0000 (14:27 +0200)]
libsoup: disable overly strict warnings, use system wide intltool.m4
When building libsoup within the SDK, the following usually nonfatal warning
is causing the build to fail:
make[6]: Entering directory '.../build_dir/target-arm_xscale_musl-1.1.14_eabi/libsoup-2.53.2/libsoup'
CC libsoup_2_4_la-soup-address.lo
cc1: error: .../staging_dir/target-arm_xscale_musl-1.1.14_eabi/include: No such file or directory [-Werror=missing-include-dirs]
cc1: some warnings being treated as errors
Makefile:962: recipe for target 'libsoup_2_4_la-soup-address.lo' failed
Use the upstream `--disable-more-warnings` configure switch to disable this
class of `-Werror` flags.
Also drop the shipped copy of `intltool.m4` to force using the system wide one
which does not require the `XML::Parser` module to be installed (see #2771).
Jo-Philipp Wich [Mon, 30 May 2016 14:27:03 +0000 (16:27 +0200)]
intltool: make dependency on XML::Parser optional
Patch `configure` and the shipped `intltool.m4` macro file to make a missing
XML::Parser perl module nonfatal.
All utilities provided by intltool are programmed to fail gracefully at run
time if the module cannot be loaded and those utilities commonly used during
the build do not require it at all.
Also drop the the build-prereq on XML::Parser now that it is optional.
Jo-Philipp Wich [Mon, 30 May 2016 10:19:10 +0000 (12:19 +0200)]
libftdi1: explicitely disable Boost unit tests
When libftdi1 is detecting the presence of the Boost unit testing framework,
it will conditionally enable the build of libftdi1 test binaries which fail to
link on some targets with the following error:
CMakeFiles/test_libftdi1.dir/basic.cpp.o: In function `main':
basic.cpp:(.text.startup+0xc): undefined reference to `boost::unit_test::unit_test_main(bool (*)(), int, char**)'
collect2: error: ld returned 1 exit status
test/CMakeFiles/test_libftdi1.dir/build.make:123: recipe for target 'test/test_libftdi1' failed
make[6]: *** [test/test_libftdi1] Error 1
Since we do not care about test cases and since we want to avoid unpredictable
conditional compilation simply disable the testcases entirely.
Michal Hrusecky [Mon, 23 May 2016 14:07:43 +0000 (16:07 +0200)]
lxc: Use more FSH compliant /srv/lxc instead of new root dir
Normally LXC uses /var/lib, but due to hack OpenWRT employs this is not an
option. But instead of introducing new top-level directory, FSH compatible /srv
can be used.
Michael Heimpold [Sat, 21 May 2016 20:12:25 +0000 (22:12 +0200)]
php5: update to 5.6.21
This fixes the following CVEs:
- in BCMath: CVE-2016-4537, CVE-2016-4538
- in EXIF: CVE-2016-4542, CVE-2016-4543, CVE-2016-4544
- in GD: CVE-2016-3074
- in Intl: CVE-2016-4540, CVE-2016-4541
- in XML: CVE-2016-4539
Jo-Philipp Wich [Fri, 20 May 2016 12:07:28 +0000 (14:07 +0200)]
lttng-tools: musl compile fixes
Add two patches to address three distinct build problems spotted by our
build bots when compiling lttng-tools:
1) unconditional use of `__GLIBC_PREREQ`
On musl based toolchains there is no such macro defined, leading to the
following preprocessor error:
CC compat-epoll.lo
In file included from compat-epoll.c:33:0:
poll.h:76:19: error: missing binary operator before token "("
#if __GLIBC_PREREQ(2, 9)
2) undeclared `mode_t` type
On musl based toolchains the `mode_t` type is not implicitely defined through
other includes, leading to the following compile error:
CC hashtable.lo
In file included from ../../../src/common/common.h:24:0,
from hashtable.c:24:
../../../src/common/runas.h:25:46: error: unknown type name 'mode_t'
int run_as_mkdir_recursive(const char *path, mode_t mode, uid_t uid, gid_t gid);
^
../../../src/common/runas.h:26:36: error: unknown type name 'mode_t'
int run_as_mkdir(const char *path, mode_t mode, uid_t uid, gid_t gid);
^
../../../src/common/runas.h:27:46: error: unknown type name 'mode_t'
int run_as_open(const char *path, int flags, mode_t mode, uid_t uid, gid_t gid);
^
3) multiple definitions
The header files declare several `const char *` pointers which are initialized
in various `*.c` files later on. Due to a missing `extern` declaration in the
header, the final linking of the executables fails with errors such as:
CCLD lttng
../../../src/common/.libs/libcommon.a(mi-lttng.o):(.data.rel.ro.local+0x0): multiple definition of `mi_lttng_element_snapshots'
commands/enable_events.o:(.bss+0x18): first defined here
collect2: error: ld returned 1 exit status
This commits addresses these issues with two patches, `100-musl-compat.patch`
fixes issue 1 by declaring a fallback dummy declaration of `__GLIBC_PREREQ` and
issue 2 by explicitely including `sys/stat.h` which provides `mode_t` according
to POSIX.
The second patch, `200-use-extern.patch` declares all char pointers in the
header file as `extern`, fixing the observed linker errors.
Jo-Philipp Wich [Thu, 19 May 2016 12:29:57 +0000 (14:29 +0200)]
tiff: fix wrong declaration of ftell() compat macro
The libtiff library declares an `ftell()` compat macro redirecting calls
to `ftello()` if such an implementation exists. The compat macro however
is declared with a wrong number of arguments, leading to the following
error on our buildbots:
In file included from .../usr/include/uClibc++/iostream:29:0,
from tif_stream.cxx:31:
.../usr/include/uClibc++/fstream:422:22: error: macro "ftell" requires 3 arguments, but only 1 given
retval = ftell(fp);
Add a patch to fix the macro definition in order to fix compilation of
the tiff package.
Jo-Philipp Wich [Thu, 19 May 2016 12:03:14 +0000 (14:03 +0200)]
mc: apply gettext version fixup
Apply the version fixup in order to solve the following build error on systems
not using exactly gettext version 0.18:
make[6]: Entering directory '.../build_dir/target-mips_34kc_musl-1.1.14/mc-4.8.17/po'
*** error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.18 but the autoconf macros are from gettext version 0.19
The fixup will ensure that embedded macro versions are replaced with the
version of the staged gettext executable in ./staging_dir/host/bin
Jo-Philipp Wich [Thu, 19 May 2016 09:41:44 +0000 (11:41 +0200)]
openconnect: avoid possible implicit dependency on liblz4
If the liblz4 library exists within the build environment, the openconnect
configure will pick it up and start depending on it, leading to the following
build error:
Package openconnect is missing dependencies for the following libraries:
liblz4.so.1
Disable LZ4 support in configure in order to avoid this implicit,
nondeterministic dependency.
Jo-Philipp Wich [Wed, 18 May 2016 12:59:16 +0000 (14:59 +0200)]
usbip: mark as nonshared
Mark the usbip package nonshared so that is built along with the target
specific binaries and not within the SDK environment.
This is needed since the usbip package draws its source files directly
from the kernel tree which is unavailable within the SDK.
Fixes the following build error encountered by the LEDE buildbots:
http://downloads.lede-project.org/snapshots/faillogs/mipsel_1004kc_dsp/packages/usbip/compile.txt