unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: guile-user@gnu.org
Subject: Re: Nyacc and guile-nearly-3.0 (progress report)
Date: Mon, 2 Dec 2019 22:45:23 +0100	[thread overview]
Message-ID: <20191202214523.GC3978@tuxteam.de> (raw)
In-Reply-To: <94784430-a9ad-bb11-f481-ef2426a6dfca@gmail.com>

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

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:

  tomas@trotzki:~/src/guile/nyacc$ ./configure
  checking for pkg-config... /usr/bin/pkg-config
  checking pkg-config is at least version 0.9.0... yes
  configure: checking for guile 3.0
  configure: found guile 3.0
  checking for guile... /usr/local/bin/guile
  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:

  tomas@trotzki:~/src/guile/nyacc$ ./configure
  checking for pkg-config... /usr/bin/pkg-config
  checking pkg-config is at least version 0.9.0... yes
  configure: checking for guile 3.0
  configure: found guile 3.0
  checking for guile... /usr/local/bin/guile
  checking for Guile version >= 3.0... configure: error: Guile 3.0 required, but 2.9.5 found
  tomas@trotzki:~/src/guile/nyacc$ ( cd etc && autoconf -o ../configure )
  tomas@trotzki:~/src/guile/nyacc$ ./configure
  checking for pkg-config... /usr/bin/pkg-config
  checking pkg-config is at least version 0.9.0... yes
  configure: checking for guile 2.9.5
  configure: found guile 2.9.5
  checking for guile... /usr/local/bin/guile
  configure: error: found development files for Guile 2.9.5, but /usr/local/bin/guile has effective version 3.0

It seems I've got a schizophrenic Guile. It somehow reports
an "effective version" 3.0 (the pkg config file in /usr/local/lib
is a guile-3.0.pc, actually), but if you ask guile itself, it
reports 2.9.5.

I don't exactly know where configure has this "effective version"
from, but I dimly remember Andy mumbling about setting Guile's
effective version to 3.0, since 2.9.5 is already a pre-3.

Hmmm. I'll try to poke at it some more tomorrow...

Cheers & thanks
-- tomás

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2019-12-02 21:45 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 [this message]
2019-12-03  9:31       ` tomas
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=20191202214523.GC3978@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).