From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 56803 invoked by alias); 7 Oct 2019 06:12:50 -0000 Mailing-List: contact libffi-discuss-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libffi-discuss-owner@sourceware.org Received: (qmail 56795 invoked by uid 89); 7 Oct 2019 06:12:50 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 spammy=HX-Languages-Length:629 X-HELO: einhorn-mail.in-berlin.de Received: from einhorn-mail.in-berlin.de (HELO einhorn-mail.in-berlin.de) (217.197.80.20) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 07 Oct 2019 06:12:48 +0000 X-Envelope-From: doko@ubuntu.com Received: from authenticated.user (localhost [127.0.0.1]) by einhorn.in-berlin.de with ESMTPSA id x976CfEV019837 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 7 Oct 2019 08:12:44 +0200 Subject: Re: State of Header installation directory ? To: Marc Ihm , libffi-discuss@sourceware.org References: From: Matthias Klose Message-ID: <8bb8c739-6ad6-844e-c497-a9abeafc5ab8@ubuntu.com> Date: Mon, 07 Oct 2019 06:12:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019/txt/msg00035.txt.bz2 On 06.10.19 19:42, Marc Ihm wrote: > Hi, > > regarding the discussion about where to install the headers (e.g. ffi.h) i am > all in favor of targeting /usr/include or another public directory. > > If I read > > https://sourceware.org/ml/libffi-discuss/2018/msg00003.html > > correctly, this has already been agreed upon. > > But still the headers are installed e.g. in > /usr/local/lib64/libffi-3.2.1/include which cannot be found by e.g. configure > > So my question: has there been any progress in this matter ? this is fixed on the trunk, and in the first 3.3 release candidate.