From: Rob Browning <rlb@defaultvalue.org>
To: guile-devel@gnu.org
Subject: Re: [PATCH 3/6] Add guile-procedures.txt to BUILT_SOURCES
Date: Mon, 01 Jul 2024 23:15:48 -0500 [thread overview]
Message-ID: <87msn0sa2z.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <20240702024708.217581-4-rlb@defaultvalue.org>
Rob Browning <rlb@defaultvalue.org> writes:
> Add guile-procedures.txt to BUILT_SOURCES to ensure it's available to
> tests. Without this, a "make check" from a clean checkout the
> "bit-extract documented?" test in bit-operations.test will fail.
>
> * Makefile.am (BUILT_SOURCES): add guile-procedures.txt
Hmm, I just did a bit more testing, and this might not be quite
right/sufficient yet.
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next prev parent reply other threads:[~2024-07-02 4:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 2:45 [PATCH 0/6] A handful of post 3.0.10 fixups Rob Browning
2024-07-02 2:45 ` [PATCH 1/6] define-meta-command: mention effects of a missing category Rob Browning
2024-07-02 2:45 ` [PATCH 2/6] Ensure GUILE-VERSION changes propagate to .version and Makefiles Rob Browning
2024-07-02 2:45 ` [PATCH 3/6] Add guile-procedures.txt to BUILT_SOURCES Rob Browning
2024-07-02 4:15 ` Rob Browning [this message]
2024-07-02 2:45 ` [PATCH 4/6] test-hashing: support 32-bit Rob Browning
2024-07-02 2:45 ` [PATCH 5/6] scm_i_utf8_string_hash: don't overrun when len is zero Rob Browning
2024-07-02 2:45 ` [PATCH 6/6] scm_i_utf8_string_hash: optimize ASCII Rob Browning
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=87msn0sa2z.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--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).