From: Trenton Henry <tbh@earthlink.net>
To: libffi-discuss@sourceware.org
Subject: maybe a bug in 3.0.13 for osx 32bit builds
Date: Thu, 17 Apr 2014 17:03:00 -0000 [thread overview]
Message-ID: <5A568FBC-5222-4207-A7EF-225B7DFC76AF@earthlink.net> (raw)
I am compiling the ffi code for osx directly into my application (as =
opposed to linking it as a library). I'm trying to build exclusively for =
32bit, on 10.9.=20
For the osx builds using the sources for libffi-3.0.13:
ffi64.c starts with
#if !defined(__i386__) && defined(__x86_64__)
as expected
ffi.c starts with
#if !defined(__i386__) && defined(__x86_64__)
but shouldn't it be
#if defined(__i386__) && !defined(__x86_64__)
Also, darwin.S starts with
#if !defined(__i386__) && defined(__x86_64__)
...
#ifndef __x86_64__
Shouldn't it also be
#if defined(__i386__) && !defined(__x86_64__)
Anyhow I made these minor changes and I got it to build and work fine. =
I'm just not certain what I did is right. It seems to make sense, but =
probably I failed to set something up right.
Thanks!
-Trenton Henry
reply other threads:[~2014-04-17 17:03 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=5A568FBC-5222-4207-A7EF-225B7DFC76AF@earthlink.net \
--to=tbh@earthlink.net \
--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).