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

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

[David Pirotte]

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

Hello Guilers,

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.

  2. By running the distributed examples.

Ultimately, one of the best way to test, and participate, is to select
G-Golf to develop the next application of your dream! Here is an
overview of the GNOME platform libraries [1], accessible using G-Golf.
In particular, libadwaita [2] provides a number of widgets that change
their layout based on the available space. This can be used to make
applications adapt their UI between desktop and mobile devices.

Contact [3]

Before you email, or bug report, you could join us on irc, and ping
me there: be patient, I also need to eat, sleep, rest ... but I always
answer, and this my preferred way to quickly interact and fix potential
G-Golf problem(s).

On irc, we chat :), so please do not write code snipsets there unless 2
or 3 lines of code, nor error messages of course - for more then 2 or 3
lines of code, or error messages, always use a tor-friendly paste
service (avoid those that track its visitors and require javascript,
thanks!).

However, if you prefer:

	G-Golf uses Guile's mailing lists
	Report bugs to bug-g-golf@gnu.org

When reporting a problem, or if you think you found a bug, it is very
important that you prepare a minimal reproducible example (MRE) [4],
sometimes also refered to as a short self-contained correct example
(SSCCE) [5].


Thanks!
David

[*] Use a .sig file to verify that the corresponding file (without the
    .sig suffix) is intact.  First, be sure to download both the .sig
    file and the corresponding tarball.  Then, run a command like this:

	gpg --verify g-golf-0.8.0-a.4.tar.gz

    If that command fails because you don't have the required public
    key, then run this command to import it:

	gpg --keyserver keys.gnupg.net --recv-keys A3057AD7

    and rerun the 'gpg --verify' command


[1] https://developer.gnome.org/documentation/introduction/overview/libraries.html
[2] https://gnome.pages.gitlab.gnome.org/libadwaita/doc/main/
[3] https://www.gnu.org/software/g-golf/contact.html
[4] https://en.wikipedia.org/wiki/Minimal_reproducible_example
[5] http://www.sscce.org/

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

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

[Aleix Conchillo Flaqué]

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)


>

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

[David Pirotte]

[-- 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 --]

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

[Aleix Conchillo Flaqué]

[-- 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 --]

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

[David Pirotte]

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

Hi Aleix,

> The Makefile.am refers to FFI_CFLAGS and FFI_CFLAGS 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)

Wow, well spotted Aleix!

The thing is, the bug never ever triggered here, not even once (in
quite a few 'build checks', in between these changes and the two next
releases: I can't explain why, just that I am using gcc and, maybe, an
unexpected(unwilling) behavior ... i  would be nice to  find out, if
anyone has an idea ... please enlighten me :), thanks.

I just pushed your proposed fix to the devel branch.

Thanks Aleix,
David

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