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: Wed, 3 May 2023 00:55:38 -0300 [thread overview]
Message-ID: <20230503005538.242ee8b8@tintin> (raw)
In-Reply-To: <CA+XASoVdvxH-y5iebOUS7au66BkiR2cELwpm2O2ec-ZK=jSrvw@mail.gmail.com>
[-- 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 --]
prev parent reply other threads:[~2023-05-03 3:55 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é
2023-05-03 3:55 ` David Pirotte [this message]
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=20230503005538.242ee8b8@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).