From: tomas@tuxteam.de
To: guile-user@gnu.org
Subject: Re: Nyacc and guile-nearly-3.0 (progress report)
Date: Tue, 3 Dec 2019 10:31:13 +0100 [thread overview]
Message-ID: <20191203093113.GB32580@tuxteam.de> (raw)
In-Reply-To: <20191202214523.GC3978@tuxteam.de>
[-- Attachment #1: Type: text/plain, Size: 1950 bytes --]
On Mon, Dec 02, 2019 at 10:45:23PM +0100, tomas@tuxteam.de wrote:
> On Mon, Dec 02, 2019 at 06:28:53AM -0800, Matt Wette wrote:
> > Look at etc/README. Maybe edit etc/configure.ac and rerun as in the README.
>
> Hm. Same confusion. Adding 3.0 to GUILE_PKG, like so:
>
> GUILE_PKG([3.0 2.2 2.0])
>
> yields, at configure time:
[...]
> checking for Guile version >= 3.0... configure: error: Guile 3.0 required, but 2.9.5 found
>
> Inserting 2.9.5 in configure.ac's GUILE_PKG, like so:
>
> GUILE_PKG([2.9.5 2.2 2.0])
>
> yields, again at configure time:
[...]
> configure: error: found development files for Guile 2.9.5, but /usr/local/bin/guile has effective version 3.0
To complement that, here what "my" Guile says:
tomas@trotzki:~$ guile
GNU Guile 2.9.5
Copyright (C) 1995-2019 Free Software Foundation, Inc.
Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
This program is free software, and you are welcome to redistribute it
under certain conditions; type `,show c' for details.
Enter `,help' for help.
scheme@(guile-user)> (version)
$1 = "2.9.5"
scheme@(guile-user)> (effective-version)
$2 = "3.0"
scheme@(guile-user)> (major-version)
$3 = "2"
scheme@(guile-user)> (minor-version)
$4 = "9"
scheme@(guile-user)> (micro-version)
$5 = "5"
This is compiled off git, specifically:
a12e862be (HEAD -> master, tag: v2.9.5, origin/master, origin/HEAD) GNU Guile 2.9.5.
Not very surprising, so far. Version is 2.9.5, "effective version" is
3.0.
As seen from my corner of reality, nyacc's configury can't cope with
the fact that Guile's version and effective version are different.
Now on your side, Mark, configury seems to get past that point (and
you run into "real" stuff, like the new shiny Guile compiler doing
"too much" at compile time -- that kind of issues one might expect).
Cheers
-- tomás
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2019-12-03 9:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 9:40 Nyacc and guile-nearly-3.0 tomas
2019-12-02 12:55 ` Nyacc and guile-nearly-3.0 (progress report) tomas
2019-12-02 14:28 ` Matt Wette
2019-12-02 21:30 ` tomas
2019-12-03 9:25 ` Arne Babenhauserheide
2019-12-03 13:33 ` Matt Wette
2019-12-03 16:44 ` tomas
2019-12-02 21:45 ` tomas
2019-12-03 9:31 ` tomas [this message]
2019-12-03 1:09 ` 2.9.5 build segfault on Ubuntu 18.04 [WAS: Nyacc and guile-nearly-3.0 (progress report)] Matt Wette
2019-12-03 16:43 ` tomas
2019-12-04 19:12 ` Nyacc and guile-nearly-3.0 Amirouche Boubekki
2019-12-04 21:04 ` tomas
2019-12-05 0:48 ` Matt Wette
2019-12-05 8:28 ` tomas
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=20191203093113.GB32580@tuxteam.de \
--to=tomas@tuxteam.de \
--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).