From: Andy Wingo <wingo@igalia.com>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 39855-done@debbugs.gnu.org
Subject: bug#39855: PKG_GUILE does not find guile
Date: Tue, 03 Mar 2020 21:26:22 +0100 [thread overview]
Message-ID: <87tv3518y9.fsf@igalia.com> (raw)
In-Reply-To: <E822078F-0101-4E60-9227-E83887F4C567@lepiller.eu> (Julien Lepiller's message of "Sun, 01 Mar 2020 07:55:04 -0500")
Julien Lepiller <julien@lepiller.eu> writes:
> I have a project I used to build with guile 2.2. I use the PKG_GUILE m4
> macro in my configure.ac. However, guile 3 comes with a guile.m4 whose
> PKG_GUILE only checks for 2.2, 2.0 and 1.8, so configure fails.
>
> Is this deprecated? Should I use something else to check for guile?
OMG I thought I had fixed this; just now pushed a patch. In the
meantime you can use GUILE_PKG([3.0 2.2]) to look for 3.0 or 2.2 (in
that order).
Thanks for the report!
Andy
prev parent reply other threads:[~2020-03-03 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-01 12:55 bug#39855: PKG_GUILE does not find guile Julien Lepiller
2020-03-01 13:17 ` Ricardo Wurmus
2020-03-03 20:26 ` Andy Wingo [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=87tv3518y9.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=39855-done@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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).