aboutsummaryrefslogtreecommitdiff
path: root/libs/libffi/Makefile
Commit message (Collapse)AuthorAge
* libffi: update to 3.4.6krant2024-02-21
| | | | Signed-off-by: krant <aleksey.vasilenko@gmail.com>
* libffi: update to 3.4.4krant2024-02-07
| | | | | | | | - Use proper tarball URL - Use HTTPS for package URL - Don't set default configure option Signed-off-by: krant <aleksey.vasilenko@gmail.com>
* treewide: assign PKG_CPE_IDFabrice Fontaine2024-02-04
| | | | Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
* treewide: refactor to use PKG_BUILD_FLAGS:=no-mips16Andre Heider2023-04-08
| | | | | | | 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>
* libffi: don't build host shared libsRosen Penev2021-10-22
| | | | | | | | Avoids rpath hacks. Add --with-pic. Needed for static library. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* libffi: bump to 3.4.2Stijn Tintel2021-08-07
| | | | | | | | 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>
* libffi: fix build failure on powerpc platformsRosen Penev2020-04-24
| | | | | | | | | 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>
* libffi: update to 3.3Rosen Penev2020-03-28
| | | | | | | | | | Remove autoreconf. autotools files are no longer patched. Add PKG_BUILD_PARALLEL for faster compilation. Removed upstreamed patches. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* libffi: do not build in a special directoryRosen Penev2020-02-13
| | | | | | There's no need. It also breaks host builds. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* libffi: fix install location of host libffi headersAlexandru Ardelean2017-08-26
| | | | | | | | | 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>
* libffi: do not append multilib suffix (eg. '../lib64') to toolexeclibdirGergely Kiss2016-05-12
| | | | Signed-off-by: Gergely Kiss <mail.gery@gmail.com>
* libffi: fix include path in pkg-config file, fixes glib2 buildFelix Fietkau2016-05-11
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* libffi: bump to version 3.2.1Alexey Brodkin2016-05-11
| | | | | | | | | 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>
* libffi: fix host buildHauke Mehrtens2015-11-21
| | | | | | | | | | | My last commit c1137b6db7c461ddc3d2ddac674ba73bc1579918 "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>
* add myself as maintainer forPeter Wagner2014-07-01
| | | | | | | | | | | | | | | | | alsa-lib glib2 libffi libsndfile libtorrent speex tcp_wrappers etherwake git nfs-kernel-server portmap rtorrent Signed-off-by: Peter Wagner <tripolar@gmx.at>
* libffi: import from packages and update to latest versionPeter Wagner2014-06-30