From: "Ludovic Courtès" <ludo@gnu.org>
To: Greg Troxel <gdt@lexort.com>
Cc: guile-devel@gnu.org
Subject: Re: GNU Guile 3.0.9rc1 available for testing!
Date: Mon, 23 Jan 2023 12:02:49 +0100 [thread overview]
Message-ID: <87bkmp344m.fsf@gnu.org> (raw)
In-Reply-To: <rmibkmqxj0o.fsf@s1.lexort.com> (Greg Troxel's message of "Sun, 22 Jan 2023 18:10:47 -0500")
Hi,
Greg Troxel <gdt@lexort.com> skribis:
> and, in guile-readline/Makefile.am I see
>
> if HAVE_READLINE
>
> SOURCES += ice-9/readline.scm
>
> and I don't see an else with EXTRA_DIST. I think it's a bug for make
> dist contents to vary with whether or not libs are available on the
> local system.
Oops, good catch. I’ve fixed the machinery to require ‘HAVE_READLINE’
when running ‘make dist’ (that sounded more reliable than duplicating
the list of source files in ‘guile-readline/Makefile.am’).
Thanks,
Ludo’.
next prev parent reply other threads:[~2023-01-23 11:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 15:58 GNU Guile 3.0.9rc1 available for testing! Ludovic Courtès
2023-01-20 16:18 ` Thompson, David
2023-01-21 14:58 ` Jan Nieuwenhuizen
2023-01-23 10:42 ` Ludovic Courtès
2023-01-23 13:23 ` Janneke Nieuwenhuizen
2023-01-20 17:50 ` Aleix Conchillo Flaqué
2023-01-23 10:45 ` Ludovic Courtès
2023-01-23 17:01 ` Aleix Conchillo Flaqué
2023-01-22 2:12 ` Greg Troxel
2023-01-22 14:30 ` lloda
2023-01-22 14:39 ` Greg Troxel
2023-01-23 10:48 ` Ludovic Courtès
2023-01-23 18:04 ` lloda
2023-01-23 21:59 ` bug#60971: build failure of v3.0.9rc1 on mac os 12.6 Ludovic Courtès
2023-01-23 18:47 ` GNU Guile 3.0.9rc1 available for testing! Aleix Conchillo Flaqué
2023-01-25 1:44 ` Greg Troxel
2023-01-25 10:32 ` Ludovic Courtès
2023-01-22 17:41 ` Greg Troxel
2023-01-22 23:10 ` Greg Troxel
2023-01-23 11:02 ` Ludovic Courtès [this message]
2023-01-23 11:19 ` Ludovic Courtès
2023-01-24 15:43 ` Greg Troxel
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=87bkmp344m.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=gdt@lexort.com \
--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).