public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Anthony Green <green@moxielogic.com>
To: noloader@gmail.com
Cc: libffi-discuss@sourceware.org
Subject: Re: Header installation directory
Date: Sun, 04 Feb 2018 01:03:00 -0000	[thread overview]
Message-ID: <CACxje5-bevrVPFc2ZeXyprBn74KkQi3zUGEA6TOhsjgAqU0FAg@mail.gmail.com> (raw)
In-Reply-To: <CAH8yC8kR_xGdXy72MZO++2VhZk1utOaZvU75d1CBVgdKdfGkiQ@mail.gmail.com>

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?

AG

On Fri, Feb 2, 2018 at 1:28 PM, Jeffrey Walton <noloader@gmail.com> wrote:
> Hi Everyone,
>
> My apologies for this question... I configured with
> --prefix=/usr/local and --libdir=/usr/local/lib64 on Fedora. Build and
> install seems to go well, but this caught my eye:
>
>     gmake[3]: Nothing to be done for 'install-exec-am'.
>      /bin/mkdir -p '/usr/local/lib64/libffi-3.2.1/include'
>      /bin/install -c -m 644 ffi.h ffitarget.h
> '/usr/local/lib64/libffi-3.2.1/include'
>
> The header file location seems a bit unusual. Are headers supposed to
> be installed below the libdir?
>
> The libffi home page does not discuss header file location, and I did
> not see an INSTALL or README to look it up. I also did not see an
> option when running ./configure --help.
>
> Looking at Stallman's
> https://www.gnu.org/software/make/manual/html_node/Directory-Variables.html
> , I don't really see a place for a version-specific set of header
> files. It looks like the convention is to overwrite old headers with
> new headers when from the same package.
>
> Thanks in advance,
>
> Jeff

  reply	other threads:[~2018-02-04  1:03 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 [this message]
2018-02-06  5:30   ` Matthias Klose

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=CACxje5-bevrVPFc2ZeXyprBn74KkQi3zUGEA6TOhsjgAqU0FAg@mail.gmail.com \
    --to=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).