This backports an upstream fix for the following warning:
Warning: Unparsable number `xu \b, dcrypt version %d'
Signed-off-by: Martin Schiller <ms@dev.tdt.de>
Notable changes:
* Use toml as new default storage backend:
Upstream has removed the ini plugin, we have been using in the
past. toml is still somewhat experimental, but upstream has
designated it as future recommended default.
* Remove the dependency on boost. The only plugin needing that has
been removed upstram.
* Enable plugins for libev and libuv event loop integration. This
adds two new packages with the respective dependencies.
Upstream has fixed the bugs preventing us from using this.
* Enable the internal notification plugin/system. This allows
applications to automatically receive notifications about changes
to their configuration. Again upstream fixing bugs enables this
for us.
* Set the environment variable $XDG_CACHE_HOME to "/tmp/" globally
to prevent elektra (and possibly other applications) from
writing temporary data to flash.
Signed-off-by: Harald Geyer <harald@ccbib.org>
Python supports both GNU dbm and Berkley DBM.
GNU dbm also has a compatibility layer for Berkeley.
The current Berkley DB in OpenWrt is 4.7 and hasn't been updated in ages.
It's also pretty big.
So, an alternative for Python is to use GNU dbm for both (GNU and Berkley).
Also, removing static shared libraries from the build, to encourage the
usage of the shared ones.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
Switch to AUTORELEASE for simplicity.
Disable parallel compilation as there's something wrong with NSS' build
system. Reliably fails with make -j 12 on a ryzen 3600.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
configure.in checks for "ARMv8 CRC32C intrinsics" and goes as far as
adding "-march=armv8-a+crc" to the target flags if the compiler allows
it. This can clash with the OpenWrt target flags in
CONFIG_TARGET_OPTIMIZATION. If for example the latter is set to
"-mcpu=cortex-a9" the following warning is issued:
cc1: warning: switch '-mcpu=cortex-a9' conflicts with '-march=armv5t' switch
This commit prevents configure.in from adding the mentioned flag. The
addition is unwanted when cross-compiling.
An issue was raised for this recently, see [1].
[1] https://github.com/openwrt/packages/issues/16034
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
I'm reverting this commit, because it is pulling newer source code, but
without doing a new version bump. This results that users who already
installed this library on their router will have different package
content than users who installed it after the commit.
The another small reason is that commit subject - update revision is cryptic itself and should be more bulletproof like saying update to version 1.1
More details: https://github.com/openwrt/packages/pull/15990#issuecomment-870333695
This reverts commit e779323481.
Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
We should use upstream patch here, which can be removed later,
instead of maintaining our own one.
Reported-by: Rosen Penev <rosenp@gmail.com>
Signed-off-by: Michael Heimpold <mhei@heimpold.de>
This patch fixes the compilation issue of the upstream Cmake file.
If this patch is not applied we get the following compilation error output.
CMake Error at cmake/ConnectorName.cmake:30 (ENDMACRO):
Flow control statements are not properly nested.
Call Stack (most recent call first):
CMakeLists.txt:423 (INCLUDE)
The blamed cmake/ConnectorName.cmake file gets fixed with this patch.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
ICU 69 updates to CLDR 39 locale data with many additions and corrections. ICU 69 also includes significant improvements for measurement unit formatting and number formatting in general, as well as many other bug fixes and enhancements.
Signed-off-by: Hirokazu MORIKAWA <morikw2@gmail.com>
domoticz wants them. No idea how to avoid it. Easier to just add back
here.
Removed several outdated options from CMake times.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
In v1.76.0 Boost.Regex became a header-only library.
With this update, there are now two different versions:
- v4 for C++03 (deprecated)
- v5 header-only
This commit fixes an issue which was preventing Boost.Regex
from being built for old ArmV5 targets
Signed-off-by: Carlos Miguel Ferreira <carlosmf.pt@gmail.com>
Remove myself as maintainer from PowerDNS Related packages and add
Peter van Dijk from PowerDNS as the new maintainer
Signed-off-by: James Taylor <james@jtaylor.id.au>
Remove celt051 option as upstream removed it.
Remove upstreamed patches.
Switch to AUTORELEASE for simplicity.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
Building the xr_usb_serial module fails for Kenel 5.10 with CONFIG_PM
enabled:
xr_usb_serial_common.c:1574:15: error: 'ASYNCB_INITIALIZED' undeclared
(first use in this function); did you mean 'RCU_INITIALIZER'?
Use tty_port_initialized in order to determine the status of the TTY
port. This is compatible with Kernel 5.10 and at least Kernel 5.4.
Signed-off-by: David Bauer <mail@david-bauer.net>
After the recent libgpg-error update, the workaround for gpgrt-config
is no more necessary.
Reverts 63481e619 ("libassuan: fix linking of host's libgpg-error").
Signed-off-by: Alexander Egorenkov <egorenar-dev@posteo.net>
Paul Blazejowski discovered that the recent update to this package broke
cross-compiling for some OpenWrt platforms. This backports commit 33593864
(March 26, 2021) from the upstream libgpg-error project to fix this
problem.
Signed-off-by: W. Michael Petullo <mike@flyn.org>
gpgrt-config is trying to use the host's /usr/lib path when looking for
libgpg-error. Therefore, disable it and gpg-error-config will be used
as a fallback.
Signed-off-by: Alexander Egorenkov <egorenar-dev@posteo.net>
Library for node.js will be disabled temporarily due to difficulty in supporting the latest node.js.
Signed-off-by: Hirokazu MORIKAWA <morikw2@gmail.com>
Library for node.js will be disabled temporarily due to difficulty in supporting the latest node.js.
Signed-off-by: Hirokazu MORIKAWA <morikw2@gmail.com>
h2o is the library dnsdist uses to offer DNS over HTTPS to clients. dnsdist is the only user of h2o in this tree.
While h2o can depend on Ruby (to build mruby support), this is disabled in the OpenWRT build of h2o. Hence, the Ruby dependency is unnecessary, and removing it saves a few megabytes of disk space.
Signed-off-by: Peter van Dijk <peter.van.dijk@powerdns.com>
This commit updates boost to version 1.76.0
There are no new libraries in this version
More info about Boost 1.76.0 can be found at the usual place [1].
Note: This package update includes a fix merged to Boost.Fiber in [2]
which did not make into this version but it will be present in the next
one. For now, the patch is needed, but it will be removed in version
1.77.0
[1]: https://www.boost.org/users/history/version_1_76_0.html
[2]: https://github.com/boostorg/fiber/pull/276
Signed-off-by: Carlos Miguel Ferreira <carlosmf.pt@gmail.com>
This enables tools again which has been disabled in commit
498506af9 ("libupnp: update to 1.14.5"). Disabling tools leads to the
header upnptools.h not being installed into /usr/include. But e.g. mpd-full
depends on this header.
Fixes: 498506af9 ("libupnp: update to 1.14.5")
Signed-off-by: Alexander Egorenkov <egorenar-dev@posteo.net>
Removed two now pointless patches as they were added as options.
Switch to AUTORELEASE for simplicity.
Update MESON_ARGS.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
This reverts commit b29e609701.
Adding DEPENDS+=@!arc will cause a circular dependency, because some
packages select libseccomp based on a build option.
Commit e29483d7e ("libseccomp: workaround a recursive dependency") added
a workaround that was not properly documented, so I'll explain here.
The problem arises when libseccomp is selected depending on some config
option:
define Pakcage/foo
DEPENDS=+FOO_SECCOMP:libseccomp
Even if the condition is correctly defined, excluding arc, such as:
define Package/foo/config
config FOO_SECCOMP
depends on !arc
the config generator will parse libseccomp's DEPENDS variable and
generate menuconfig statements like these:
config PACKAGE_foo
select PACKAGE_libseccomp if FOO_SECCOMP
depends on !FOO_SECCOMP || !arc
The last condition is always true because FOO_SECCOMP will always be
be false when arc is true. The config generator is not able to
simplify/optimize the condition.
The circular dependecy occurs because FOO_SECCOMP depends on
PACKAGE_foo, and the redundant, always true line will make PACKAGE_foo
depend on FOO_SECCOMP.
As a workaround, we can add the 'depends on !arc' line to
Package/libseccomp/config, outside of the DEPENDS variable, so that the
redundant depends line line does not get generated.
Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
Cc: Daniel Golle <daniel@makrotopia.org>
