buildroot/package/libffi, branch 2015.11

package/libffi: bump to version 3.2.1

2015-09-20T12:30:21+00:00

Also: - unfuzz patches #1 and #2 - remove applied patches upstream Signed-off-by: Jörg Krause Signed-off-by: Thomas Petazzoni

libffi: add hash file

2015-04-07T20:06:41+00:00

Signed-off-by: Gustavo Zacarias Signed-off-by: Thomas Petazzoni

package/*: rename patches according to the new policy

2015-02-03T13:52:56+00:00

Autogenerated from rename-patch.py (http://patchwork.ozlabs.org/patch/403345) Signed-off-by: Samuel Martin Signed-off-by: Peter Korsgaard

.mk files: bulk aligment and whitespace cleanup of assignments

2014-10-07T13:00:28+00:00

The Buildroot coding style defines one space around make assignments and does not align the assignment symbols. This patch does a bulk fix of offending packages. The package infrastructures (or more in general assignments to calculated variable names, like $(2)_FOO) are not touched. Alignment of line continuation characters (\) is kept as-is. The sed command used to do this replacement is: find * -name "*.mk" | xargs sed -i \ -e 's#^$[A-Z0-9a-z_]\+$\s*$[?:+]\?=$\s*$#\1 \2#' -e 's#^$[A-Z0-9a-z_]\+$\s*$[?:+]\?=$\s*$[^\\]\+$$#\1 \2 \3#' -e 's#^$[A-Z0-9a-z_]\+$\s*$[?:+]\?=$\s*$[^\\ \t]\+\s*\\$\s*$#\1 \2 \3#' -e 's#^$[A-Z0-9a-z_]\+$\s*$[?:+]\?=$$\s*\\$#\1 \2\3#' Brief explanation of this command: ^$[A-Z0-9a-z_]\+$ a regular variable at the beginning of the line $[?:+]\?=$ any assignment character =, :=, ?=, += $[^\\]\+$ any string not containing a line continuation $[^\\ \t]\+\s*\\$ string, optional whitespace, followed by a line continuation character $\s*\\$ optional whitespace, followed by a line continuation character Hence, the first subexpression handles empty assignments, the second handles regular assignments, the third handles regular assignments with line continuation, and the fourth empty assignments with line continuation. This expression was tested on following test text: (initial tab not included) FOO = spaces before FOO = spaces before and after FOO = tab before FOO = tab and spaces before FOO = tab after FOO = tab and spaces after FOO = spaces and tab after FOO = \ FOO = bar \ FOO = bar space \ FOO = \ GENIMAGE_DEPENDENCIES = host-pkgconf libconfuse FOO += spaces before FOO ?= spaces before and after FOO := FOO = FOO = FOO = FOO = $(MAKE1) CROSS_COMPILE=$(TARGET_CROSS) -C AT91BOOTSTRAP3_DEFCONFIG = \ AXEL_DISABLE_I18N=--i18n=0 After this bulk change, following manual fixups were done: - fix line continuation alignment in cegui06 and spice (the sed expression leaves the number of whitespace between the value and line continuation character intact, but the whitespace before that could have changed, causing misalignment. - qt5base was reverted, as this package uses extensive alignment which actually makes the code more readable. Finally, the end result was manually reviewed. Signed-off-by: Thomas De Schampheleire Cc: Yann E. Morin Cc: Thomas Petazzoni Signed-off-by: Peter Korsgaard

libffi and python: need threads support

2014-09-13T07:40:48+00:00

libffi depends on pthreads. Python depends on libffi (it can provide a builtin libffi, but also depends on pthreads). Thus this patch also disable Python support if toolchain is compiled w/o treads support. Fixes http://sysmic.org/~jezz/results/204099dd: ../src/closures.c:119:21: fatal error: pthread.h: No such file or directory [Peter: fix comment dependencies, add python3] Signed-off-by: Jérôme Pouiller Signed-off-by: Peter Korsgaard

package: remove the trailing slash sign from _SITE variable

2014-07-31T21:17:46+00:00

Since the trailing slash is stripped from $($(PKG)_SITE) by pkg-generic.mk: $(call DOWNLOAD,$($(PKG)_SITE:/=)/$($(PKG)_SOURCE)) so it is redundant. This patch removes it from $(PKG)_SITE variable for BR consistency. Signed-off-by: Jerzy Grzegorek Signed-off-by: Thomas Petazzoni

libffi: remove some header files installed in /usr/lib in the target

2014-07-01T12:56:51+00:00

For some reason, libffi installs some header files in /usr/lib/libffi-/include, which is a non-standard location and therefore they do not get removed automatically by the target-finalize logic. This commit adds a post-install hook in libffi.mk to get rid of these unneeded headers on the target. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

libffi: bump to 3.1

2014-07-01T12:52:40+00:00

Status of the patches: - libffi-001-Fix-installation-location-of-libffi.patch, preserved. - libffi-002-Fix-use-of-compact-eh-frames-on-MIPS.patch, preserved - libffi-arc-01-Add-ARC-support.patch, removed, ARC support was merged upstream as of commit b082e15091961373c03d10ed0251f619ebb6ed76. - libffi-arc-02-Rebuild-for-ARC-additions.patch, removed, this patch was merged upstream as of commit 0f8690a84c874ec09a090c8c6adfb93c594acac6. - libffi-003-fix-typo.patch, added, reported on the upstream mailing list as being necessary, will be part of the next 3.1.1 release. - libffi-004-Add-missing-GNU-stack-markings-in-win32.S.patch, same status as patch 003. - libffi-005-Fix-paths-in-libffi.pc.in.patch, same status as patch 003. The 3.1 release adds support for a number of architectures: ARC support, ppc64le support, NIOS II support. See https://sourceware.org/ml/libffi-announce/2014/msg00000.html for details. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

libffi: back-port support for ARC

2014-05-29T20:15:00+00:00

Support for ARC CPUs was added in libffi after 3.0.13 vesion was cut and up until now no new release has been done. So to enale libffi on ARC we need this set of patches. These are corrsponding commits in libffi: * b082e15091961373c03d10ed0251f619ebb6ed76 - Add ARC support * 0f8690a84c874ec09a090c8c6adfb93c594acac6 - Rebuild for ARC additions * d918d47809c174d62283306b282749f8db93661f - arc: Fix build error The first patch was modified a bit (cut changelog part) to accomodate changes not related to ARC between 3.0.14 and changes in question. Signed-off-by: Alexey Brodkin Signed-off-by: Misca Jonker Cc: Peter Korsgaard Cc: Gustavo Zacarias Signed-off-by: Peter Korsgaard

package: drop unneeded HOST__AUTORECONF = YES

2013-10-04T12:57:38+00:00

Since 97c687000 (pkg-autotools.mk: default host AUTORECONF{,_OPT} to the target values) we automatically enable autoreconf for host builds if it is enabled for the target, so these can go. Signed-off-by: Peter Korsgaard