From: Rob Browning <rlb@defaultvalue.org>
To: 36808-done@debbugs.gnu.org
Cc: DongChan LEE <derick.lee@samsung.com>
Subject: bug#36808: Unable to find GNU libunistring when building Guile 2.2.6
Date: Fri, 12 Jul 2024 20:12:28 -0500 [thread overview]
Message-ID: <87a5imw0w3.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <87o8uvb1qn.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 22 Jan 2020 22:49:36 +0100")
I'm closing this, suspecting that the issue has been resolved in newer
versions of Guile or the platform, or... But please feel free to
re-open it if that's mistaken.
Thanks
--
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
prev parent reply other threads:[~2024-07-13 1:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190725062118epcms2p428338ca6f48cf46b58894db6f3383dd3@epcms2p4>
2019-07-25 6:21 ` bug#36808: Unable to find GNU libunistring when building Guile 2.2.6 DongChan LEE
2020-01-22 21:49 ` Ludovic Courtès
2024-07-13 1:12 ` Rob Browning [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=87a5imw0w3.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=36808-done@debbugs.gnu.org \
--cc=derick.lee@samsung.com \
/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).