This issue was introduced after upgrading to 3.8.
Patch `006-remove-multi-arch-and-local-paths.patch` was dropped. It was
tested on x86, but when using the x86_64 compiler in OpenWrt, the issue is
present.
The issue seems to be about Ubuntu/Debian's multi-arch support in
Python/Python3 setup [which I forgot about]. The code runs it regardless of
whether it cross-compiles or not, and for OpenWrt, this causes issues, as
it introduces absolute include paths from the host system.
Dirk Brenken [Sun, 3 Nov 2019 15:44:22 +0000 (16:44 +0100)]
banip: update 0.3.5
* fix race condition in download utility detection during boot
* fix multiple possible bugs in ipset creation
* prevent parallel service starts
* refine service trigger handling
* add ssh daemon auto detection
* print to stdout if 'logger' is not available
objects/fileio.o: In function `readfile':
fileio.c:(.text+0x5b3f): undefined reference to `libiconv_close'
fileio.c:(.text+0x61ad): undefined reference to `libiconv_close'
fileio.c:(.text+0x62f6): undefined reference to `libiconv'
fileio.c:(.text+0x6794): undefined reference to `libiconv_close'
objects/fileio.o: In function `buf_write_bytes':
fileio.c:(.text+0xa1fe): undefined reference to `libiconv'
fileio.c:(.text+0xa54a): undefined reference to `libiconv'
objects/fileio.o: In function `buf_write':
fileio.c:(.text+0xaf48): undefined reference to `libiconv_close'
objects/mbyte.o: In function `my_iconv_open.part.18':
mbyte.c:(.text+0x2ced): undefined reference to `libiconv_open'
mbyte.c:(.text+0x2d3a): undefined reference to `libiconv'
mbyte.c:(.text+0x2d5f): undefined reference to `libiconv_close'
objects/mbyte.o: In function `convert_setup_ext':
mbyte.c:(.text+0x33bf): undefined reference to `libiconv_close'
objects/mbyte.o: In function `string_convert_ext':
mbyte.c:(.text+0x363c): undefined reference to `libiconv'
collect2: error: ld returned 1 exit status
link.sh: Linking failed
Makefile:1949: recipe for target 'vim' failed
This is addressed by pulling in libiconv/host. Also configure switches
are added that keep external dependencies to a minimum, for instance
avoiding to link to X11 or gettext.
* libsane dependency on libusb moved to those drivers that requires it
* clean up some ./configure args
* added saned-ricoh2 for new backend
* enabled saned-gphoto2 (after c8fbe26c532aced97ab8a4d42f1289db2a3e6d65)
* disabled kvs40xx and mustek_usb2 that requires pthread while the issue is
not solved (https://gitlab.com/sane-project/backends/issues/153)
* patches refreshed:
- 002-remove-uneeded.patch
* patches dropped:
- 031-fix_uclibc.patch
- 050-remove_linked_libs_for_unused_preload.patch (with --disable-preload)
Signed-off-by: Luiz Angelo Daros de Luca <redacted>
Alberto Bursi [Thu, 31 Oct 2019 13:03:47 +0000 (14:03 +0100)]
modemmanager: enable mbim/qmi support by default
MBIM and QMI support (necessary for modern and
high-performance LTE modems) should be default
y otherwise the only way to use modemmanager
with these protocols is to recompile the package.
This is very inconvenient for most end users.
Ansuel Smith [Fri, 25 Oct 2019 01:27:03 +0000 (03:27 +0200)]
nginx: adds ubus external module
- Adds ubus module to nginx
- Select module by default
- Adds script to detect ubus module and append config for luci
- Switch all external module to xz
Saverio Proto [Tue, 29 Oct 2019 08:59:37 +0000 (09:59 +0100)]
tinc: fix build regression in pkg 1.0.36-1
the patches 010-Fix-compilation-when-OpenSSL-has-no-ENGINE-support
and 020-Fix-compilation-without-deprecated-OpenSSL-APIs are now
merged upstream, so they must be dropped from the OpenWrt pkg
Sebastian Kemper [Mon, 28 Oct 2019 18:36:15 +0000 (19:36 +0100)]
libqmi: fix compile on build bots
On the OpenWrt build bots the compile currently fails:
cc1: error: /builder/shared-workdir/build/sdk/staging_dir/target-arm_cortex-a5+vfpv4_musl_eabi/include: No such file or directory [-Werror=missing-include-dirs]
cc1: all warnings being treated as errors
(Or rather, it _would_ fail like this if libmbim compiled successfully.)
The directory in question gets added to TARGET_CPPFLAGS by rules.mk.
Nothing usually gets installed to that directory, so unsurprisingly it
may not exist on the build bots.
On first glance this problem cannot be reproduced. But once autoreconf
is called this becomes possible.
If called without "--enable-more-warnings", configure adds -Werror to
the flags. This commit adds "--enable-more-warnings=yes" to the build.
This way the extra warnings are kept in place, but they aren't turned
into errors no more.
"PKG_FIXUP:=autoreconf" is also added so that it's easier to forecast
build failures on the build bots when preparing future pull request.
Last but not least "--disable-silent-rules" is added, because more
output is usually welcome for debugging, be it on the build bots or at
home/the office.
Sebastian Kemper [Mon, 28 Oct 2019 18:21:42 +0000 (19:21 +0100)]
libmbim: fix compile on build bots
On the OpenWrt build bots the compile currently fails:
make[8]: Entering directory '/builder/shared-workdir/build/sdk/build_dir/target-arm_cortex-a5+vfpv4_musl_eabi/libmbim-1.20.0/src/common'
CC libmbim_common_la-mbim-common.lo
cc1: error: /builder/shared-workdir/build/sdk/staging_dir/target-arm_cortex-a5+vfpv4_musl_eabi/include: No such file or directory [-Werror=missing-include-dirs]
cc1: all warnings being treated as errors
The directory in question gets added to TARGET_CPPFLAGS by rules.mk.
Nothing usually gets installed to that directory, so unsurprisingly it
may not exist on the build bots.
On first glance this problem cannot be reproduced. But once autoreconf
is called this becomes possible.
If called without "--enable-more-warnings", configure adds -Werror to
the flags. This commit adds "--enable-more-warnings=yes" to the build.
This way the extra warnings are kept in place, but they aren't turned
into errors no more.
"PKG_FIXUP:=autoreconf" is also added so that it's easier to forecast
build failures on the build bots when preparing future pull request.
Last but not least "--disable-silent-rules" is added, because more
output is usually welcome for debugging, be it on the build bots or at
home/the office.
2.6.5 fixes:
* CVE-2019-16255: A code injection vulnerability of Shell#[] and Shell#test
* CVE-2019-16254: HTTP response splitting in WEBrick (Additional fix)
* CVE-2019-15845: A NUL injection vulnerability of File.fnmatch and File.fnmatch?
* CVE-2019-16201: Regular Expression Denial of Service vulnerability of WEBrick’s Digest access authentication
2.6.4 fixes:
* Multiple jQuery vulnerabilities in RDoc
git.99rst.org / openwrt-packages.git / log