gnunet's config section may contain dashes '-' which isn't an
allowed character for sections in UCI.
Thus replace the first underscore with a dash which in gnunet-config
sections, as that happends to be work for all currently used sections.
e.g. this now allows accessing sections like transport-http_server via
an UCI sections called transport_http_server as well as namestore-flat
using an UCI section called namestore_flat.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
some general packaging fixes for cadet and conversation.
allow building experimental components multicast, psyc, social.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Main changes are as the following
- Allow specifying port in server option, e.g. example.com:1702 (fixes
github issue #1960 "xl2tpd port change bug").
- Fixes NULL dereference on connection timeout
- Update 100-makefile_opt_flags.patch
Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* import from oldpackages
* bump version and update hash
* update patch to new version
* add PKG_LICENSE, PKG_LICENSE_FILES, PKG_MAINTAINER
Signed-off-by: Phil Eichinger <phil@zankapfel.net>
Configuration scripts expect the libc identifier to be "uclibc" in case we're using it,
OpenWrt provides "uClibc". Oh well...
Signed-off-by: Marcel Denia <naoir@gmx.net>
perl: Set gccversion configuration symbol correctly
This was previously manually set to '4.8.0'. Aside from just being incorrect,
it also breaks Errno's GCC5 detection.
Fixes #2044.
Signed-off-by: Marcel Denia <naoir@gmx.net>
Minor fixes:
- CoRoutine2 selector requires that a GCC v5 compiler or better is selected
- coroutine2 requires C++14
- The Makefile was not alowing the libraries to be compiled with both
statically and shared, at the same time. There are now two seperate options,
allowing to select which version is wanted.
- The Makefile was also not allowing to compile both single thread and multi-
thread versions. Again, two seperate options now exist.
- There is also the option to build another set of libraries with debug support
which is good for development.
- These options are important for those who whish to build an OpenWRT SDK.
Signed-off-by: Carlos M. Ferreira <carlosmf.pt@gmail.com>
Jo-Philipp Wich