See commit 5c545bdb "treewide: replace PKG_USE_MIPS16:=0 with
PKG_BUILD_FLAGS:=no-mips16" on the main repository.
Signed-off-by: Andre Heider <a.heider@gmail.com>
Remove both patches as they have been upstreamed.
This new release is only available on Github and does not ship configure
or Makefile, so autoreconf is needed.
Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
The crude loop I wrote to come up with this changeset:
find -L package/feeds/packages/ -name patches | \
sed 's/patches$/refresh/' | sort | xargs make
Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
This is an upstream backport.
Currently on the buildbots, having libffi unavailable leads to long
range build failures.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
Seems that the header files for the host libffi headers
are installed in the wrong place.
i.e. $(STAGING_DIR_HOSTPKG)/lib/libffi-3.2.1/include
when it should be $(STAGING_DIR_HOSTPKG)/include
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
Among many fixes and improvements this new version adds
support of ARC architecture (ARC port was actually introduced
in v3.1 but while at it why not to update to the most recent version).
Which allows to build dependent projects like Python etc.
Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
My last commit c1137b6db7 "libffi: fix
libffi.pc file" broke the host build as that still placed the header
files to /usr/lib/libffi-3.0.13/include/ and the libffi.pc file pointed
to /usr/include/ . With this patch I took the patch from Debian and
also made the install process to put the header files to /usr/include
in all situations.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
The include dir pointed to staging_dir/target-mips_34kc+dsp_musl-1.1.11
/usr/lib/libffi-3.0.13/include which does not exists, this made glib2
fail to compile. The header files are copied to /usr/include so define
it in the libffi.pc file.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
krant