Removed upstreamed patches. Also fixes a redefinition error on some
platforms.
Cleaned up the DEPENDS to be simpler and more concise.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
Added $(TARGET_CPPFLAGS) to TARGET_CFLAGS to fix a buildbot failure to
find oniguruma include files.
Signed-off-by: Eneas U de Queiroz <cote2004-github@yahoo.com>
The first and last hunks of the patch were already taken care of, but
the middle two were still needed.
Signed-off-by: Eneas U de Queiroz <cote2004-github@yahoo.com>
Versions earlier than 1.2.15 had security vulnerabilities, especially
related to the bundled oniguruma. Now libevhtp uses a system-provided
library instead. The API changed as well, requiring patches to
seafile-server.
Adds @cotequeiroz Eneas U de Queiroz as maintainer.
Signed-off-by: Eneas U de Queiroz <cote2004-github@yahoo.com>
oniguruma is a regular expression library for different character
encodings.
It is a dependency of current version of libevhtp, and is currently only
producing a static library, not generating an installable package.
Signed-off-by: Eneas U de Queiroz <cote2004-github@yahoo.com>
Forum user portuquesa raised a topic (see [1]) about being unable to use
Asterisk on his armeb xscale device. We narrowed it down to sqlite3.
Asterisk was unable to insert a simple table into its db.
In short, sqlite3 assumes little endian for every ARM device. This
worked OK for 4 Byte bit (unaligned) access. But once upstream (back in
2015) added a function which accesses 2 Bytes (see [2]) this failed for
some (if not all) ARM big endian devices. ARM CPUs are bi-endian for 4
Byte reads but not for 2 Byte reads.
This patch fixes the problem by setting the endianness adequately for
ARM targets, for both 32 bit and 64 bit varieties. The patch was applied
upstream (see [3]).
[1] https://forum.openwrt.org/t/solved-asterisk13-or-15-sqlite3-database-problem/36856
[2] https://github.com/sqlite/sqlite/commit/329428e2088aabb1db2dc6e48108b76551405a8e
[3] https://www.sqlite.org/src/info/b7aad929619f7043
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Pull request #9033 showed that there are problems with builds where
thread-safe mode is disabled. The binaries still reference functions
from libpthread. This commit removes the thread-safe choice for now.
Once this is addressed upstream the choice can be added back.
Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
Libevhtp is building a static library, used by seafile-server.
Every time the libevhtp binary changes, seafile-server needs a release
bump.
Leave a note in the libevhtp Makefile, as a reminder.
Signed-off-by: Eneas U de Queiroz <cote2004-github@yahoo.com>
Patch was posted on the mailing list. Awaits inclusion looks like. Fixes
long range build failures on the platform.
Updated Mirror list. The first two seem to not work.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
Maintainer: me
Correct issues with TITLE and add URL pointing to the fstrm GitHub Page. Reformat the description so it renders correctly in menuconfig.
Fixes#9022
Signed-off-by: James Taylor <james@jtaylor.id.au>
fstrm is an optimized C implementation of Frame Streams that includes a fast, lockless circular queue implementation and exposes library interfaces for setting up a dedicated Frame Streams I/O thread and asynchronously submitting data frames for transport from worker threads. It was originally written to facilitate the addition of high speed binary logging to DNS servers written in C using the dnstap log format.
Maintainer: me
Compile Tested: armv7l, SNAPSHOT 655fff1571 SDK
Run Tested: armv7l, Linksys WRT1900ACS, OpenWrt SNAPSHOT, r9987-655fff1571
Signed-off-by: James Taylor <james@jtaylor.id.au>
Description from Amol Bhave:
This package fails to compile with boost 1.70 when the boost cmake
config gets used.
As far as I can tell, Boost 1.70 introduced
BoostConfigVersion.cmake. In that file, the value of PACKAGE_VERSION is
set to 1.70. This makes CMake auto set the variable Boost_VERSION to
1.70. Historically, Boost_VERSION has been using the format like 170000,
and not 1.70. Some package cmake files still depend on this behavior
and make assertions such as Boost_VERSION > 168000. This is incompatible
with the new scheme.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
Description from Amol Bhave:
This package fails to compile with boost 1.70 when the boost cmake
config gets used.
As far as I can tell, Boost 1.70 introduced
BoostConfigVersion.cmake. In that file, the value of PACKAGE_VERSION is
set to 1.70. This makes CMake auto set the variable Boost_VERSION to
1.70. Historically, Boost_VERSION has been using the format like 170000,
and not 1.70. Some package cmake files still depend on this behavior
and make assertions such as Boost_VERSION > 168000. This is incompatible
with the new scheme.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
Rosen Penev