public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: saleem gagguturu <saleemgagguturu@live.com>
To: "libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>
Subject: Cross compiling for iOS
Date: Thu, 1 Feb 2024 07:04:31 +0000	[thread overview]
Message-ID: <PU4P216MB209967FF5138F2CAD4F40721C5432@PU4P216MB2099.KORP216.PROD.OUTLOOK.COM> (raw)

[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]

Hi,

I'm trying to cross-compile libffi for iOS from Debian. I managed to cross-compile it successfully for MacOS (arm64 and x86) using OSX Cross but I'm getting some errors for iOS.

My configure command is:

./configure --host=arm-apple-darwin11 --prefix=$IOS_TOOLCHAIN_ROOT --libdir=$IOS_TOOLCHAIN_ROOT/lib --disable-docs

This is the error I'm getting:


libtool: link: ( cd ".libs" && rm -f "libffi_convenience.la" && ln -s "../libffi_convenience.la" "libffi_convenience.la" )
Undefined symbols for architecture arm64:
  "_ffi_call", referenced from:
      _ffi_raw_call in raw_api.o
      _ffi_java_raw_call in java_raw_api.o
  "_ffi_closure_trampoline_table_page", referenced from:
      _ffi_closure_alloc in closures.o
  "_ffi_prep_cif_machdep", referenced from:
      _ffi_prep_cif_core in prep_cif.o
  "_ffi_prep_cif_machdep_var", referenced from:
      _ffi_prep_cif_core in prep_cif.o
  "_ffi_prep_closure_loc", referenced from:
      _ffi_prep_closure in prep_cif.o
      _ffi_prep_raw_closure_loc in raw_api.o
      _ffi_prep_raw_closure in raw_api.o
      _ffi_prep_java_raw_closure_loc in java_raw_api.o
      _ffi_prep_java_raw_closure in java_raw_api.o
ld: symbol(s) not found for architecture arm64

I've raised an issue with full logs here https://github.com/libffi/libffi/issues/821

Anyone know any workaround for this? I need libffi as it's a dependency to Glib.

Thanks


             reply	other threads:[~2024-02-01  7:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01  7:04 saleem gagguturu [this message]
2024-02-03  2:11 ` Russell Keith-Magee

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=PU4P216MB209967FF5138F2CAD4F40721C5432@PU4P216MB2099.KORP216.PROD.OUTLOOK.COM \
    --to=saleemgagguturu@live.com \
    --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).