From: Matthias Klose <doko@ubuntu.com>
To: Anthony Green <green@moxielogic.com>, noloader@gmail.com
Cc: libffi-discuss@sourceware.org
Subject: Re: Header installation directory
Date: Tue, 06 Feb 2018 05:30:00 -0000 [thread overview]
Message-ID: <8699c1b4-a39d-408b-a66e-b99f9f6e2a89@ubuntu.com> (raw)
In-Reply-To: <CACxje5-bevrVPFc2ZeXyprBn74KkQi3zUGEA6TOhsjgAqU0FAg@mail.gmail.com>
On 04.02.2018 02:03, Anthony Green wrote:
> Jeffrey Walton <noloader@gmail.com> writes:
>
>> The header file location seems a bit unusual. Are headers supposed to
>> be installed below the libdir?
>
> Hi Jeff,
>
> Thanks for your note. See this thread for background info:
>
> https://sourceware.org/ml/libffi-discuss/2017/msg00000.html
>
> It's likely that nobody cares about multi-arch headers anymore, so maybe
> we should just forget about this and dump the arch specific headers in
> /usr/include.
>
> Would anybody object?
They should be installed in standard locations. However that change should not
be backported to the GCC sources. Btw, do you plan to backport the recent libffi
development to be used in GCC 8?
Matthias
prev parent reply other threads:[~2018-02-06 5:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 18:28 Jeffrey Walton
2018-02-04 1:03 ` Anthony Green
2018-02-06 5:30 ` Matthias Klose [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=8699c1b4-a39d-408b-a66e-b99f9f6e2a89@ubuntu.com \
--to=doko@ubuntu.com \
--cc=green@moxielogic.com \
--cc=libffi-discuss@sourceware.org \
--cc=noloader@gmail.com \
/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).