From: Marc Ihm <marc@ihm.name>
To: libffi-discuss@sourceware.org
Subject: Re: State of Header installation directory ?
Date: Tue, 08 Oct 2019 04:07:00 -0000 [thread overview]
Message-ID: <1c7ab9cc-d8ab-87f0-7838-b39e51bc9a4a@ihm.name> (raw)
In-Reply-To: <8bb8c739-6ad6-844e-c497-a9abeafc5ab8@ubuntu.com>
Great ! Thank you.
Am 07.10.2019 um 08:12 schrieb Matthias Klose:
> 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.
prev parent reply other threads:[~2019-10-08 4:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 17:42 Marc Ihm
2019-10-07 6:12 ` Matthias Klose
2019-10-08 4:07 ` Marc Ihm [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1c7ab9cc-d8ab-87f0-7838-b39e51bc9a4a@ihm.name \
--to=marc@ihm.name \
--cc=libffi-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).