unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
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 14:34:50 -0300	[thread overview]
Message-ID: <20230501143450.6cff3d96@tintin> (raw)
In-Reply-To: <CA+XASoWSCWd5+YSEywPjBs87St6CSaQH+Hs1_x7HWQkXG10eyw@mail.gmail.com>

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

Hi Aleix,

> 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.

David

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-05-01 17:34 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 [this message]
2023-05-01 20:33     ` Aleix Conchillo Flaqué
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=20230501143450.6cff3d96@tintin \
    --to=david@altosw.be \
    --cc=aconchillo@gmail.com \
    --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).