From: Uli Link <ul.mcamafia@linkitup.de>
To: libffi-discuss@sourceware.org
Cc: usmc_1811@sbcglobal.net, dwitte@gmail.com
Subject: Building 3.0.10rc5 on AIX 5.2 or newer
Date: Fri, 25 Feb 2011 21:42:00 -0000 [thread overview]
Message-ID: <4D682228.3060407@linkitup.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 389 bytes --]
I forgot about a slight difference between AIX 5.1 and earlier and AIX
5.2 and later:
AIX 5.2 introduced the C99 runtime and headers, so ffi.h.in needs a
further patch to compile with IBM XLC on AIX 5.2 or later which has
LLONG_MAX.
Sorry, I only tested on my Mozilla build host running AIX 5.1 :-(
AIX native preprocessor needs non-integer literals properly suffixed.
--
Uli Link
[-- Attachment #2: libffi-ffi_h_in.patch --]
[-- Type: text/plain, Size: 1007 bytes --]
diff -U 8 -p libffi-3.0.10rc5.org/include/ffi.h.in libffi-3.0.10rc5/include/ffi.h.in
--- libffi-3.0.10rc5.org/include/ffi.h.in 2011-02-13 14:05:35.000000000 +0100
+++ libffi-3.0.10rc5/include/ffi.h.in 2011-02-25 22:14:10.000000000 +0100
@@ -81,21 +81,25 @@ extern "C" {
#define FFI_64_BIT_MAX 9223372036854775807
#ifdef LONG_LONG_MAX
# define FFI_LONG_LONG_MAX LONG_LONG_MAX
#else
# ifdef LLONG_MAX
# define FFI_LONG_LONG_MAX LLONG_MAX
+# ifdef _AIX52 /* or newer has C99 LLONG_MAX */
+# undef FFI_64_BIT_MAX
+# define FFI_64_BIT_MAX 9223372036854775807LL
+# endif /* _AIX52 or newer */
# else
# ifdef __GNUC__
# define FFI_LONG_LONG_MAX __LONG_LONG_MAX__
# endif
-# ifdef _AIX
+# ifdef _AIX /* AIX 5.1 and earlier have LONGLONG_MAX */
# ifndef __PPC64__
# if defined (__IBMC__) || defined (__IBMCPP__)
# define FFI_LONG_LONG_MAX LONGLONG_MAX
# endif
# endif /* __PPC64__ */
# undef FFI_64_BIT_MAX
# define FFI_64_BIT_MAX 9223372036854775807LL
# endif
reply other threads:[~2011-02-25 21:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4D682228.3060407@linkitup.de \
--to=ul.mcamafia@linkitup.de \
--cc=dwitte@gmail.com \
--cc=libffi-discuss@sourceware.org \
--cc=usmc_1811@sbcglobal.net \
/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).