From: Andy Wingo <wingo@pobox.com>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: Andy Wingo <wingo@pobox.com>, Guile User <guile-user@gnu.org>,
guile-sources@gnu.org, guile-devel <guile-devel@gnu.org>
Subject: Re: GNU Guile 2.9.8 Released [beta]
Date: Sun, 05 Jan 2020 11:41:26 +0100 [thread overview]
Message-ID: <87sgkuyyll.fsf@pobox.com> (raw)
In-Reply-To: <CAPjoZofgK=+nixNgZvZNWApm9+mU4C2ce_WYHqeuAYTkBcx_1g@mail.gmail.com> (Nala Ginrut's message of "Fri, 3 Jan 2020 13:34:59 +0800")
On Fri 03 Jan 2020 06:34, Nala Ginrut <nalaginrut@gmail.com> writes:
> When I was trying to compile Artanis, the configure threw an error:
> ----------------------------
> checking for Guile version >= 3.0... configure: error: Guile 3.0 required, but 2.9.8 found
> ----------------------------
>
> Here's what I put in configure.ac:
> GUILE_PKG(2.2 2.3 2.9 3.0)
>
> My question is "what's the correct config here"?
There was a bug in guile.m4 from a few years ago doesn't do the right
thing for major version changes. I think you need to update guile.m4
from git, then do:
GUILE_PKG([2.2 3.0])
Also note that it's not meaningful to put in alpha releases to GUILE_PKG
-- 2.9.7's effective version is 3.0.
FWIW I would encourage doing GUILE_PKG([3.0 2.2]) instead, as it's
generally the right thing to default to newer Guile release series.
Cheers,
Andy
next prev parent reply other threads:[~2020-01-05 10:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 13:36 GNU Guile 2.9.8 Released [beta] Andy Wingo
2020-01-03 5:34 ` Nala Ginrut
2020-01-03 9:02 ` tomas
2020-01-03 14:29 ` Matt Wette
2020-01-03 14:53 ` Matt Wette
2020-01-03 18:44 ` configuring guile packages [was: GNU Guile 2.9.8 Released [beta]] Matt Wette
2020-01-03 23:29 ` Matt Wette
2020-01-06 6:56 ` Nala Ginrut
2020-01-08 14:21 ` Nala Ginrut
2020-01-08 18:24 ` Jason Earl
2020-01-08 18:43 ` Nala Ginrut
2020-01-05 10:41 ` Andy Wingo [this message]
2020-01-07 20:00 ` GNU Guile 2.9.8 Released [beta] Stefan Israelsson Tampe
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=87sgkuyyll.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=guile-sources@gnu.org \
--cc=guile-user@gnu.org \
--cc=nalaginrut@gmail.com \
/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).