From: Thorsten Kukuk <kukuk@suse.de>
To: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: nscd broken...
Date: Wed, 18 Feb 2004 18:06:00 -0000 [thread overview]
Message-ID: <20040218180645.GA14226@suse.de> (raw)
In-Reply-To: <m3u11o9su7.fsf@gromit.moeb>
On Wed, Feb 18, Andreas Jaeger wrote:
>
> nscd does not build, it fails with:
>
> nscd_conf.c: In function `nscd_parse_file':
> nscd_conf.c:59: warning: implicit declaration of function `__fsetlocking'
> nscd_conf.c:59: error: `FSETLOCKING_BYCALLER' undeclared (first use in this function)
> nscd_conf.c:59: error: (Each undeclared identifier is reported only once
> nscd_conf.c:59: error: for each function it appears in.)
Use this:
--- nscd/nscd_conf.c
+++ nscd/nscd_conf.c 2004/02/17 14:45:50
@@ -21,6 +21,7 @@
#include <malloc.h>
#include <pwd.h>
#include <stdio.h>
+#include <stdio_ext.h>
#include <stdlib.h>
#include <string.h>
#include <libintl.h>
--
Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de
SuSE Linux AG Maxfeldstr. 5 D-90409 Nuernberg
--------------------------------------------------------------------
Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
prev parent reply other threads:[~2004-02-18 18:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 17:59 Andreas Jaeger
2004-02-18 18:06 ` Thorsten Kukuk [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=20040218180645.GA14226@suse.de \
--to=kukuk@suse.de \
--cc=libc-hacker@sources.redhat.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).