public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Samuli Suominen <ssuominen@gentoo.org>
To: libffi-discuss@sourceware.org
Subject: Re: [PATCH] Use $CFLAGS to calculate multi_os_directory in configure.ac.
Date: Mon, 03 Mar 2014 13:44:00 -0000	[thread overview]
Message-ID: <53148681.8010001@gentoo.org> (raw)
In-Reply-To: <20140303133421.GA339@linux.vnet.ibm.com>


On 03/03/14 15:34, Dominik Vogt wrote:
> On Mon, Mar 03, 2014 at 03:02:47PM +0200, Samuli Suominen wrote:
>> On 03/03/14 14:56, Dominik Vogt wrote:
>>> While we're talking about installations paths:  "make istall"
>>> should really install ffi.h to <prefix>/include/libffi... and not
>>> to <prefix>/lib/libffi.../include.  It doen't respect --installdir=
>>> either.
>> The headers are arch specific and belong to libdir.
> Still, "./configure --help" claims that --includedir= works, but it
> doesn't:
>
>  $ ./configure --help
>  ...
>  --includedir=DIR        C header files [PREFIX/include]
>                          ^^^^^^^^^^^^^^
>
> Ciao
>
> Dominik ^_^  ^_^
>

I hear you. Indeed, there should be an ./configure switch to override
the default. But since not everyone
is realizing the headers are arch specific, there should at the very
least be ./configure --help 'information'
about to let people know it's not a good idea.
Possibly it shouldn't be --includedir=, but something like
--with-override-includedir=
Likewise for --with-override-libdir= for the other case of multi os
directory

  reply	other threads:[~2014-03-03 13:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-03 12:36 Dominik Vogt
2014-03-03 12:41 ` Samuli Suominen
2014-03-03 12:43   ` Samuli Suominen
2014-03-03 12:56     ` Dominik Vogt
2014-03-03 13:05       ` Samuli Suominen
2014-03-03 13:34         ` Dominik Vogt
2014-03-03 13:44           ` Samuli Suominen [this message]
2014-03-03 14:10         ` Anthony Green
2014-03-12  6:49 ` [PING 1][PATCH] " Dominik Vogt

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=53148681.8010001@gentoo.org \
    --to=ssuominen@gentoo.org \
    --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).