For consistency, use full name instead of $(PKG_NAME) in define and eval
lines for all packages.
I've seen reviews that asked to do this before, and I am asking the same
during reviews now. To avoid this in the future, fix this treewide so
when people use existing packages as example, we will not have to
request this change anymore.
This makes all packages consistent with both LEDE and OpenWrt base
repositories.
Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
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
