FreshPorts -- devel/libffi

The libffi library provides a portable, high level programming interface to various calling conventions. This allows a programmer to call any function specified by a call interface description at run time. WWW: http://sources.redhat.com/libffi/

pkg-plist

make generate-plist

Expand this list (18 items)

/usr/local/share/licenses/libffi-3.2.1_2/catalog.mk

/usr/local/share/licenses/libffi-3.2.1_2/LICENSE

/usr/local/share/licenses/libffi-3.2.1_2/MIT

include/ffi.h

include/ffitarget.h

lib/libffi-3.2.1/include/ffi.h

lib/libffi-3.2.1/include/ffitarget.h

lib/libffi.a

lib/libffi.so

lib/libffi.so.6

lib/libffi.so.6.0.4

libdata/pkgconfig/libffi.pc

man/man3/ffi.3.gz

man/man3/ffi_call.3.gz

man/man3/ffi_prep_cif.3.gz

man/man3/ffi_prep_cif_var.3.gz

@postexec /sbin/ldconfig -m /usr/local/lib

@postunexec /sbin/ldconfig -R

Collapse this list.

To install the port: cd /usr/ports/devel/libffi/ && make install clean
To add the package: pkg install libffi

NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.

Apply upstream change from libffi to check for HAVE_AS_X86_PCREL for all x86 targets. This should eliminate any text relocations, in particular for the i386 build, making it possible to build the port with lld without having to use -z notext. Obtained from: https://github.com/libffi/libffi/pull/174 Approved by: zeising (maintainer) PR: 214864 MFH: 2017Q4

MASTER_SITES cleanup. - Replace ${MASTER_SITE_FOO} with FOO. - Merge MASTER_SITE_SUBDIR into MASTER_SITES when possible. (This means 99.9% of the time.) - Remove occurrences of MASTER_SITE_LOCAL when no subdirectory was present and no hint of what it should be was present. - Fix some logic. - And generally, make things more simple and easy to understand. While there, add magic values to the FESTIVAL, GENTOO, GIMP, GNUPG, QT and SAMBA macros. Also, replace some EXTRACT_SUFX occurences with USES=tar:*. Checked by: make fetch-urlall-list With hat: portmgr Sponsored by: Absolight

Update libffi to 3.2.1 - Add LICENSE_FILE - Use OPTIONS helpers - Backport: Fix for testsuite using clang [1] - Backport: Fix build with Clang 3.5 on ARM [2] PR: 196408 Submitted by: koobs Approved by: mentor (implicit) Relnotes: yes

devel/libffi: Fix abort() on ARM related to __clear_cache() The current FreeBSD/ARM __clear_cache() implementation does nothing #if __i386__ || __x86_64__ #else abort(); cognet@ advises this is an issue for anything !Apple that is using the libcompiler_rt provided by Clang on ARM, and requires upstreaming. Additionally, two Python ports (python26 and python31) use devel/libffi for unrelated reasons, so this addresses the related PR for those ports too [2]. - Enable STAGE support - Remove MAN* entries and update pkg-plist accordingly - Add LICENSE - Sort USE/USES section - Use install-strip as the INSTALL_TARGET PR: ports/149167 PR: ports/184517 [2] Approved by: maintainer timeout (2 weeks)

This changes almost all the "gnomehack" only USE_GNOME cases to USES= pathfix. If a port used other USE_GNOME items it was untouched. The ports that used other USES were fixed by hand. PR: ports/177081 Reviewed by: bapt Approved by: portmgr (miwi)

- Update to 3.0.12 - Remove patches that were included upstream - Rename TEST option to TESTS - Add TEST_DEPENDS & regression-test: target - Remove post-build: so tests dont run unconditionally Approved by: eadler Discussed with: kwm, milki, flo, pgj

$CFLAGS are redundant for compiling .s files. GCC stays quiet, but Clang gives a warning of unused arguments. The configure check greps for warning, so the check fails. Remove $CFLAGS to clang doesn't emit the warnings. PR: ports/152480 Submitted by: me Patch by: dim@ Approved by: maintainer

- Update to 3.0.1 - Pass maintainership to submitter PR: ports/120736 Submitted by: Bjorn Konig <bkoenig@alpha-tierchen.de> Approved by: Horance Chou <horance@freera.net> (maintainer)

Mass-conversion to the USE_AUTOTOOLS New World Order. The code present in bsd.autotools.mk essentially makes this a no-op given that all the old variables set a USE_AUTOTOOLS_COMPAT variable, which is parsed in exactly the same way as USE_AUTOTOOLS itself. Moreover, USE_AUTOTOOLS has already been extensively tested by the GNOME team -- all GNOME 2.12.x ports use it. Preliminary documentation can be found at: http://people.FreeBSD.org/~ade/autotools.txt which is in the process of being SGMLized before introduction into the Porters Handbook. Light blue touch-paper. Run.

Apply a big libtool patch to allow porters to use the libtool installed by the libtoolX ports instead of the one included with each port. Ports that set USE_LIBTOOL_VER=X will now use the ports version of libtool instead of the included version. To restore previous behavior, use the new macro, USE_INC_LIBTOOL_VER. Both macros accept the same argument: a libtool version. For example, to use the ports version of libtool-1.5, add the following to your Makefile: USE_LIBTOOL_VER= 15 To use the included version of libtool with extra hacks provided by libtool-1.5, add the following to your Makefile: USE_INC_LIBTOOL_VER= 15 With this change, ports that had to add additional libtool hacks to prevent .la files from being installed or to fix certain threading issues can now delete those hacks (after appropriate testing, of course). PR: 63944 Based on work by:eik and marcus Approved by: ade (autotools maintainer) Tested by: kris on pointyhat Bound to be hidden problems: You bet

Whoa there, boy, that's a mighty big commit y'all have there... Begin autotools sanitization sequence by requiring ports to explicitly specify which version of {libtool,autoconf,automake} they need, erasing the concept of a "system default". For ports-in-waiting: USE_LIBTOOL=YES -> USE_LIBTOOL_VER=13 USE_AUTOCONF=YES -> USE_AUTOCONF_VER=213 USE_AUTOMAKE=YES -> USE_AUTOMAKE_VER=14 Ports attempting to use the old style system after June 1st 2004 will be sorely disappointed.