Update:
- Python 3.6 support fixed. It is now correctly compiled and available.
Fixes:
- disabled context and fiber for unsupported targets
There are several architectures which are not supported by context nor
fiber. Because of this, Boost build was failing targets. This created the
situation where the other boost libs were not being built and consequently,
becoming unavailable at the OpenWRT/LEDE repositories.
To solve this issue, it was necessary to disabled fiber and context for
the incompatible targets.
Boost.Fiber is disabled for:
-> ar7, rb532, brcm63xx.smp, brcm63xx, brcm47xx, brcm47xx.legacy, brcm2708,
au1000, ath25, adm8668 and adm5120.
Boost.Context is disabled for:
-> avr32, octeon and netlogic.
Signed-off-by: Carlos Miguel Ferreira <carlosmf.pt@gmail.com>
This commit fixes an existent regression in boost 1.63 [1].
The regression appears when libc is used for the toolchain.
[1] - https://svn.boost.org/trac/boost/ticket/11756
Signed-off-by: Carlos Miguel Ferreira <carlosmf.pt@gmail.com>
Need PCRE2 library for the fish shell. Took existing pcre makefile
as a base to build pcre2, supporting 8, 16, and 32 bit characters with
different install targets for each.
Signed-off-by: Shane Peelar <lookatyouhacker@gmail.com>
Maintainer: me
Compile tested: brcm2708
aarch64_cortex-a53+neon-vfpv4_musl
LEDE head r3426-4c09f99
Run tested: NONE
Description: buildbots fail on link ARM object.
error: xxxxxx.o uses VFP register arguments,
Signed-off-by: Hirokazu MORIKAWA <morikw2@gmail.com>
libidn.pc file was missing in package staging area causing build
failures for other packages expecting to find libidn package config
files.
refreshed patches to clear existing patch fuzz
take over maintainership
Signed-off-by: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
While fixing up some incorrect STAGING_DIR_HOSTPKG uses I introduced, I
noticed that the LIBPNG12_CONFIG variable is not used by libgd anymore (it
is called LIBPNG_CONFIG now).
As the build runs fine without setting LIBPNG_CONFIG, let's just remove the
unused line.
Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
Do not override configure recipe and do not invoke upstream autogen.sh.
The shipped autogen.sh attempts to call "gtkdocize" which is no guaranteed
build prereq of LEDE or OpenWrt.
Also add a patch to disable the processing of documentation, tests and
examples as these resources rely on gtk-doc infrastructure which is not
available within LEDE or OpenWrt.
Example error for the bad autogen.sh invocation:
( cd .../loudmouth-1.5.3; ./autogen.sh )
./autogen.sh: 33: ./autogen.sh: gtkdocize: not found
Makefile:73: recipe for target '.../.configured_yynyyyyn' failed
Example error for the lacking gtk-doc automake infrastructure:
automake: error: cannot open < gtk-doc.make: No such file or directory
autoreconf: .../host/bin/automake failed with exit status: 1
[...]
config.status: error: cannot find input file: `docs/reference/Makefile.in'
Makefile:72: recipe for target '.../.configured_yynyn' failed
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
Update libcap to upstream release 2.25
Since the libattr thing was dropped upstream in [1] it is also removed here.
Then, to overcome an issue in cross-compiling [2], set the Make parameter
according to [3].
Take maintainership of this package.
Signed-off-by: Paul Wassi <p.wassi@gmx.at>
[1]:
http://git.kernel.org/cgit/linux/kernel/git/morgan/libcap.git/commit/?id=85f38a573fc47472ab792e813b6f6b6f0b1df112
[2]:
libcap: progs/Makefile:30 executes the cross-compiled binary on the host
[3]:
libcap: Make.Rules: comment from lines 74-81
v1.6.1:
- Faster VP9 encoding and decoding
- Bug Fixes
Now the ABI_VERSION is derived from PKG_VERSION
Signed-off-by: Luiz Angelo Daros de Luca <luizluca@gmail.com>
Host files installed in Build/InstallDev are target-specific and will stay
in $(STAGING_DIR)/host after the STAGING_DIR_HOSTPKG unification.
Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
Host files installed in Build/InstallDev are target-specific and will stay
in $(STAGING_DIR)/host after the STAGING_DIR_HOSTPKG unification.
Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
Maintainer: @nxhack
Compile tested: ar71xx mips_24kc_musl-1.1.15 LEDE r2610-324bdf3
Run tested: NONE
Description:
icu: Bumped to v58.2
for emoji handling
previous PR #2817
add patches/001-disable-strtod_l.patch
missing xlocale.h in case of using musl.
Signed-off-by: Hirokazu MORIKAWA <morikw2@gmail.com>
Use bz2 instead of gz tarball, saves about 900kbyte in size
Do minor adjustments to download URL
Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
As both LEDE and OpenWrt have STAGING_DIR_HOSTPKG now, we can start to rely
on it. See 73b7f55424 for more information on
STAGING_DIR_HOSTPKG.
STAGING_DIR_HOSTPKG won't actually be changed before the first LEDE release
(it is equivalent to $(STAGING_DIR)/host), so this simple search/replace
cleanup is safe to apply. Doing this cleanup now will be useful for the
Gluon project (an OpenWrt/LEDE based firmware framework) for experimenting
with modifying STAGING_DIR_HOSTPKG before doing this in the LEDE upstream.
Also fixes a typo in the dbus Makefile ("STAGIND_DIR").
Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
Fixes build error:
```
x86_64-openwrt-linux-musl-gcc -L/home/sandu/work/lede/staging_dir/target-x86_64_musl-1.1.15/usr/lib -L/home/sandu/work/lede/staging_dir/target-x86_64_musl-1.1.15/lib -L/home/sandu/work/lede/staging_dir/toolchain-x86_64_gcc-5.4.0_musl-1.1.15/usr/lib -L/home/sandu/work/lede/staging_dir/toolchain-x86_64_gcc-5.4.0_musl-1.1.15/lib -znow -zrelro -fPIC -shared -Wl,--version-script=libfdt/version.lds -Wl,-soname,libfdt.so.1 -o libfdt/libfdt-1.4.2.so libfdt/fdt.o libfdt/fdt_ro.o libfdt/fdt_wip.o libfdt/fdt_sw.o libfdt/fdt_rw.o libfdt/fdt_strerror.o libfdt/fdt_empty_tree.o libfdt/fdt_addresses.o
/home/sandu/work/lede/staging_dir/toolchain-x86_64_gcc-5.4.0_musl-1.1.15/lib64/gcc/x86_64-openwrt-linux-musl/5.4.0/../../../../x86_64-openwrt-linux-musl/bin/ld: libfdt/fdt.o: relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC
libfdt/fdt.o: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
Makefile:283: recipe for target 'libfdt/libfdt-1.4.2.so' failed
make[4]: *** [libfdt/libfdt-1.4.2.so] Error 1
```
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
Update to 3.16.0
Add following optimizations:
HAVE_ISNAN
HAVE_MALLOC_USABLE_SIZE
Link: https://www.sqlite.org/compile.html
Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
Maintainer: @ClaymorePT
Compile tested: Broadcom BCM2708
Run tested: None
Description:
This package update contains no new libraries.
Information about the 1.63.0 release (updated libraries, bug fixes, etc), can be found here [1].
[1]: http://www.boost.org/users/history/version_1_63_0.html
Signed-off-by: Carlos Ferreira <carlosmf.pt@gmail.com>
This should fix the build on LEDE buildbots which bail out with:
-snip-
...
! -d ./src/ ] || cp -fpR ./src/* /data/bowl-builder/arm_arm926ej-s/build/ (wrapped)
sdk/build_dir/target-arm_arm926ej-s_musl-1.1.15_eabi/libcanfestival-8bfe0ac0
Applying ./patches/001-sigval-ref-fix.patch using plaintext:
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/drivers/timers_unix/timers_unix.c
|+++ b/drivers/timers_unix/timers_unix.c
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
Patch failed! Please fix ./patches/001-sigval-ref-fix.patch!
...
-snap-
Reason is, that the tar ball created by hg checkout does not contain the
version string appended to the root source directory as expected by
default PKG_BUILD_DIR, so this patch adjusts the expected directory name.
Signed-off-by: Michael Heimpold <mhei@heimpold.de>
libcoap is not building in LEDE any more because it is extracted to
/libcoap/ and the package makefiles try to access it at
/libcoap-2da31de732c0e51a9bc9e1d4aea21e25da89cf87/.
This patch defines a PKG_BUILD_DIR variable to make it use /libcoap/
without the hash.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Some parts of boost need at least C++11, activate -std=gnu++14
when possible and otherwise use -std=gnu++11 instated of using the
default which is -std=gnu++98.
This fixes the build for me when I build everything expect
boost-coroutine2 with gcc 5.4.0 on LEDE.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>