public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mingli.yu at windriver dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nscd/29051] nscd: No such file or directory
Date: Tue, 14 Jun 2022 01:59:52 +0000 [thread overview]
Message-ID: <bug-29051-131-77Zn4fEdnj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29051-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29051
--- Comment #3 from Mingli <mingli.yu at windriver dot com> ---
(In reply to Andreas Schwab from comment #2)
> Please report that to the provider of lib32-nscd.
We build the lib32-nscd ourselves from the latest source
git://sourceware.org/git/glibc.git.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-06-14 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 2:34 [Bug nscd/29051] New: " mingli.yu at windriver dot com
2022-04-14 3:08 ` [Bug nscd/29051] " mingli.yu at windriver dot com
2022-06-13 11:03 ` schwab@linux-m68k.org
2022-06-14 1:59 ` mingli.yu at windriver dot com [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-29051-131-77Zn4fEdnj@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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).