From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31976 invoked by alias); 12 Feb 2013 12:44:44 -0000 Received: (qmail 31949 invoked by uid 22791); 12 Feb 2013 12:44:43 -0000 X-SWARE-Spam-Status: No, hits=-5.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_BF X-Spam-Check-By: sourceware.org Received: from mail-wi0-f176.google.com (HELO mail-wi0-f176.google.com) (209.85.212.176) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 12 Feb 2013 12:44:35 +0000 Received: by mail-wi0-f176.google.com with SMTP id hm14so4356115wib.3 for ; Tue, 12 Feb 2013 04:44:33 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.101.98 with SMTP id ff2mr3300593wib.0.1360673073756; Tue, 12 Feb 2013 04:44:33 -0800 (PST) Received: by 10.194.179.130 with HTTP; Tue, 12 Feb 2013 04:44:33 -0800 (PST) In-Reply-To: <511A35DC.7060207@ubuntu.com> References: <511A35DC.7060207@ubuntu.com> Date: Tue, 12 Feb 2013 12:44:00 -0000 Message-ID: Subject: Re: [patch] [libffi] do not install libffi library, headers and documentation From: Richard Biener To: Matthias Klose Cc: GCC Patches , GCJ-patches , "libffi-discuss@sourceware.org" Content-Type: text/plain; charset=ISO-8859-1 Mailing-List: contact java-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-patches-owner@gcc.gnu.org X-SW-Source: 2013-q1/txt/msg00013.txt.bz2 On Tue, Feb 12, 2013 at 1:30 PM, Matthias Klose 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?) Richard. > Matthias >