Date: Sat, 17 May 2008 15:00:04 GMT From: "Bjoern Koenig" <bkoenig@alpha-tierchen.de> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/123756: [patch] put devel/libffi includes in sane place Message-ID: <200805171500.m4HF04iV017671@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/123756; it has been noted by GNATS. From: "Bjoern Koenig" <bkoenig@alpha-tierchen.de> To: bug-followup@FreeBSD.org Cc: mjl@luckie.org.nz Subject: Re: ports/123756: [patch] put devel/libffi includes in sane place Date: Sat, 17 May 2008 16:51:21 +0200 (CEST) Hello Matthew, when I started with creating the ports libffi-devel and later libffi 3 I used /usr/local/include, as you suggest now. So I have the same feeling as you that this location would be a better place. With 3.0.4 I deceided to use /usr/local/lib/libffi-%%PORTVERSION%%/include because this location is designated by the authors of libffi and basically I do not like the idea that every distribution make idiosyncratic adjustments. I asked Anthony Green (the initial author of libffi) about the reason for this location and he answered that some distributions can potentially install different versions of libffi in lib/ and lib64/ for example. I know that this does not apply to FreeBSD, but I think that the current location does not hurt since software developers always have to use pkg-config in case their software relies on libffi. Ports like lang/squeak should do it in the same manner as I did it with java/jamvm and java/sablevm. Do you still have another reason except sanity? ;-) I'm thinking about it. I tend to move the headers to /usr/local/include and update the port to 3.0.5 briefly. Björn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200805171500.m4HF04iV017671>