From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: David Pirotte <david@altosw.be>
Cc: guile-user <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: GNU G-Golf 0.8.0-a.4 available for testing
Date: Mon, 1 May 2023 13:33:18 -0700 [thread overview]
Message-ID: <CA+XASoVdvxH-y5iebOUS7au66BkiR2cELwpm2O2ec-ZK=jSrvw@mail.gmail.com> (raw)
In-Reply-To: <20230501143450.6cff3d96@tintin>
[-- Attachment #1: Type: text/plain, Size: 1648 bytes --]
On Mon, May 1, 2023 at 10:35 AM David Pirotte <david@altosw.be> wrote:
> Hi Aleix,
>
>
Hi there!
> > Making install in libg-golf
> >
> > CC libg_golf_la-gg-ffi.lo
> > CC libg_golf_la-gg-utils.lo
> > CC libg_golf_la-gg-glib.lo
> > CC libg_golf_la-gg-gobject.lo
> > CC libg_golf_la-gg-callback.lo
> > CC libg_golf_la-gg-test-suite.lo
> > CC libg_golf_la-g-golf.lo
> > CCLD libg-golf.la
> > Undefined symbols for architecture arm64:
> > "_ffi_prep_cif", referenced from:
> > _gg_ffi_prep_cif in libg_golf_la-gg-ffi.o
> > (maybe you meant: _gg_ffi_prep_cif)
> > ld: symbol(s) not found for architecture arm64
> > clang: error: linker command failed with exit code 1 (use -v to see
> > invocation)
>
> The gg-ffi.c[h] files were changed after 0.8.0-a.2, introducing those
> new functions, see commit 15e689d3446632d4a78e4b02c20495b4b0a4ba22
> Jan the 16th 2023.
>
> I would recommend to uninstall g-golf, clear your cache(s), clear the
> build repo and try again.
>
>
I cleaned everything up and had the same issue. This time I investigated a
bit.
The Makefile.am refers to FFI_CFLAGS and FFI_LIBS, but I don't see any
reference to them and there's no PKG_CHECK_MODULES or anything that could
define those in configure.ac or any m4 macro.
Adding PKG_CHECK_MODULES line solved the issue:
PKG_CHECK_MODULES(FFI, libffi >= 3.3.0)
In 0.8.0-a.2 I guess libffi was really not used yet and as long as you had
the header file you were fine.
Let me know if this makes sense or if I'm missing something.
Thank you!
Aliex
[-- Attachment #2: Type: text/html, Size: 4513 bytes --]
next prev parent reply other threads:[~2023-05-01 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 2:50 GNU G-Golf 0.8.0-a.4 available for testing David Pirotte
2023-04-30 4:25 ` Aleix Conchillo Flaqué
2023-05-01 17:34 ` David Pirotte
2023-05-01 20:33 ` Aleix Conchillo Flaqué [this message]
2023-05-03 3:55 ` David Pirotte
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+XASoVdvxH-y5iebOUS7au66BkiR2cELwpm2O2ec-ZK=jSrvw@mail.gmail.com' \
--to=aconchillo@gmail.com \
--cc=david@altosw.be \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.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).