From: "Ludovic Courtès" <ludo@gnu.org>
To: Z572 <873216071@qq.com>
Cc: 59736-done@debbugs.gnu.org
Subject: bug#59736: [PATCH] gnu: libtirpc: fix cross-compilation.
Date: Mon, 05 Dec 2022 17:55:52 +0100 [thread overview]
Message-ID: <87o7shokmf.fsf@gnu.org> (raw)
In-Reply-To: <tencent_949B81A9E1596F7FF93A86E53B255BB5E408@qq.com> (873216071@qq.com's message of "Thu, 1 Dec 2022 16:43:34 +0800")
Hi,
Z572 <873216071@qq.com> skribis:
> * gnu/packages/onc-rpc.scm (libtirpc)[native-inputs]: add mit-krb5.
Applied, thanks!
Ludo’.
prev parent reply other threads:[~2022-12-05 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 8:43 [bug#59736] [PATCH] gnu: libtirpc: fix cross-compilation Z572 via Guix-patches via
2022-12-05 16:55 ` Ludovic Courtès [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7shokmf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=59736-done@debbugs.gnu.org \
--cc=873216071@qq.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).