From: Andy Wingo <wingo@pobox.com>
To: David Pirotte <david@altosw.be>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Master- patch - Fixing GUILE_PROGS wrong versioning checks
Date: Mon, 27 Jun 2016 10:07:25 +0200 [thread overview]
Message-ID: <87vb0v837m.fsf@pobox.com> (raw)
In-Reply-To: <20160625232841.7423f304@capac> (David Pirotte's message of "Sat, 25 Jun 2016 23:28:41 -0300")
On Sun 26 Jun 2016 04:28, David Pirotte <david@altosw.be> writes:
> From 2d1593a6f9c7fc5f1636f9695e8685fcc6334cfd Mon Sep 17 00:00:00 2001
> From: David Pirotte <david@altosw.be>
> Date: Sat, 25 Jun 2016 23:07:48 -0300
> Subject: [PATCH 3/3] Fixing GUILE_PROGS wrong versioning checks
>
> * meta/guile.m4: Fixing GUILE_PROGS versioning checks were wrong and
> incomplete, leading to false errors like: "... checking for Guile
> version >= 2.0.11... configure: error: Guile 2.0.11 required, but
> 2.1.3 found".
>
> thanks to Colomban Wendling, aka b4n, who also suggested this fix
> during a chat on #autotools while helping me wrt another autotool
> related problem I was nvestigating.
Applied, thanks :)
Andy
prev parent reply other threads:[~2016-06-27 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-26 2:28 Master- patch - Fixing GUILE_PROGS wrong versioning checks David Pirotte
2016-06-27 8:07 ` 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=87vb0v837m.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=david@altosw.be \
--cc=guile-devel@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).