This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch] [libffi] do not install libffi library, headers and documentation
- From: Richard Biener <richard dot guenther at gmail dot com>
- To: Matthias Klose <doko at ubuntu dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, GCJ-patches <java-patches at gcc dot gnu dot org>, "libffi-discuss at sourceware dot org" <libffi-discuss at sourceware dot org>
- Date: Tue, 12 Feb 2013 13:45:45 +0100
- Subject: Re: [patch] [libffi] do not install libffi library, headers and documentation
- References: <511A35DC.7060207@ubuntu.com> <CAFiYyc1RD88sGeA995Nds3ffkBmUWXVDBpAxW0pmeVUKhoO+8w@mail.gmail.com>
On Tue, Feb 12, 2013 at 1:44 PM, Richard Biener
<richard.guenther@gmail.com> wrote:
> On Tue, Feb 12, 2013 at 1:30 PM, Matthias Klose <doko@ubuntu.com> wrote:
>> The libffi library, headers and documentation are still installed, although
>> libffi provides separate releases for a long time. So do not install these
>> anymore as part of a GCC install. Tested with a build and an install with go
>> and java enabled (both using libffi_convenience). Ok for the trunk?
>
> openSUSE is using the GCC provided libffi, so no, this is not ok (not at this
> stage anyway). Also proper not-installing libffi would work by disabling
> the maybe-install-target-libffi at the toplevel, not changing libffi makfiles
> (which are supposed to be imported from upstream, no?)
Thus, add no_install= true; to the libffi target module
> Richard.
>
>> Matthias
>>