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:05:00 -0000 [thread overview]
Message-ID: <53147D77.50605@gentoo.org> (raw)
In-Reply-To: <20140303125625.GA18044@linux.vnet.ibm.com>
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.
>
> Ciao
>
> Dominik ^_^ ^_^
>
The headers are arch specific and belong to libdir. The use of
pkg-config is mandatory:
<snip>
$ grep include /usr/lib/pkgconfig/libffi.pc
includedir=${libdir}/libffi-3.0.13/include
Cflags: -I${includedir}
$ pkg-config --cflags-only-I libffi
-I/usr/lib64/libffi-3.0.13/include
$ diff -ur /usr/lib32/libffi-3.0.13 /usr/lib64/libffi-3.0.13
diff -ur /usr/lib32/libffi-3.0.13/include/ffi.h
/usr/lib64/libffi-3.0.13/include/ffi.h
--- /usr/lib32/libffi-3.0.13/include/ffi.h 2013-10-19
16:20:31.091611936 +0300
+++ /usr/lib64/libffi-3.0.13/include/ffi.h 2013-10-19
16:20:31.239611933 +0300
@@ -58,8 +58,8 @@
#endif
/* Specify which architecture libffi is configured for. */
-#ifndef X86
-#define X86
+#ifndef X86_64
+#define X86_64
#endif
/* ---- System configuration information
--------------------------------- */
</snip>
I'm sorry but this has been discussed in this very ML many times
already, I'm just pointing
the conclusion.
- Samuli
next prev parent reply other threads:[~2014-03-03 13:05 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 [this message]
2014-03-03 13:34 ` Dominik Vogt
2014-03-03 13:44 ` Samuli Suominen
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=53147D77.50605@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).