guile-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNU G-Golf 0.8.0-a.4 available for testing


From: Aleix Conchillo Flaqué
Subject: Re: GNU G-Golf 0.8.0-a.4 available for testing
Date: Sat, 29 Apr 2023 21:25:32 -0700



On Sun, Apr 16, 2023 at 7:51 PM David Pirotte <david@altosw.be> wrote:
Hello Guilers,


Hi David,
The fourth alpha release of the upcoming GNU G-Golf 0.8.0 release is
now available for testing:

-]      Tarball and a GPG detached signature [*]:

                http://ftp.gnu.org/gnu/g-golf/g-golf-0.8.0-a.4.tar.gz
                http://ftp.gnu.org/gnu/g-golf/g-golf-0.8.0-a.4.tar.gz.sig

-]      Dependencies and complete installation instructions are given
        in the distributed INSTALL file, or here:

                https://www.gnu.org/software/g-golf/install.html

-]      The list of noteworthy changes since version 0.8.0-a.3 are
        given in the distributed NEWS file, or here:

                https://www.gnu.org/software/g-golf/news.html

You can help by:

  1. Testing by installing from the tarball, or from the source if you
  prefer, on the distro of your choice.


I haven't had time to check what's going on but in case it sounds familiar I just ran into the following (it was not happening with 0.8-a.2). This is on macOS 13.3.1, glib 2.76.2:

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)



reply via email to

[Prev in Thread] Current Thread [Next in Thread]