From: "Gabor Z. Papp" <gzp@papp.hu>
To: linux-hotplug@vger.kernel.org
Subject: Re: inotify_init failed
Date: Thu, 13 Nov 2008 14:03:31 +0000 [thread overview]
Message-ID: <x6k5b7soy4@gzp> (raw)
In-Reply-To: <x6wsfaxolc@gzp>
* "Kay Sievers" <kay.sievers@vrfy.org>:
| Ah, seems inotify headers from glibc have been not available during
| compilation of udev, and inotify got disabled. You can safely ignore
| the misleading error message, I fixed the message for the next
| version.
GNU C Library stable release version 2.3.6, by Roland McGrath et al.
Which is the minimum required glibc release for compiling udev?
next prev parent reply other threads:[~2008-11-13 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 15:35 inotify_init failed Gabor Z. Papp
2008-11-11 15:45 ` Kay Sievers
2008-11-12 14:24 ` Gabor Z. Papp
2008-11-13 0:46 ` Kay Sievers
2008-11-13 14:03 ` Gabor Z. Papp [this message]
2008-11-13 14:17 ` Kay Sievers
2008-11-13 14:20 ` Gabor Z. Papp
2008-11-13 14:22 ` Kay Sievers
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=x6k5b7soy4@gzp \
--to=gzp@papp.hu \
--cc=linux-hotplug@vger.kernel.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 NNTP newsgroup(s).