From: "Gabor Z. Papp" <gzp@papp.hu>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 133 release
Date: Thu, 20 Nov 2008 21:23:01 +0000 [thread overview]
Message-ID: <x6tza2m6ru@gzp> (raw)
In-Reply-To: <1226976996.4861.14.camel@nga>
gcc -DHAVE_CONFIG_H -I. -I.. -include ../config.h -DSYSCONFDIR=\""/etc"\" -DUDEV_PREFIX=\"""\" -D_LIBUDEV_COMPILATION -g -O2 -MT libudev-device-db-write.o -MD -MP -MF .deps/libudev-device-db-write.Tpo -c -o libudev-device-db-write.o `test -f 'lib/libudev-device-db-write.c' || echo './'`lib/libudev-device-db-write.c
In file included from ./udev.h:25,
from lib/libudev-device-db-write.c:27:
./udev-sysdeps.h: In function 'inotify_init':
./udev-sysdeps.h:36: error: 'errno' undeclared (first use in this function)
./udev-sysdeps.h:36: error: (Each undeclared identifier is reported only once
./udev-sysdeps.h:36: error: for each function it appears in.)
./udev-sysdeps.h:36: error: 'ENOSYS' undeclared (first use in this function)
make[3]: *** [libudev-device-db-write.o] Error 1
make[3]: Leaving directory `/home/gzp/src/udev-133/udev'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/gzp/src/udev-133/udev'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/gzp/src/udev-133'
make: *** [all] Error 2
[kernel]
Linux gzp1 2.6.27.5-gzp1 #1 SMP Tue Nov 11 13:14:36 CET 2008 i686 GNU/Linux
[glibc]
GNU C Library stable release version 2.3.6, by Roland McGrath et al.
Compiled by GNU CC version 4.1.2.
Compiled on a Linux 2.4.34-gzp1 system on 2007-04-04.
[gcc]
gcc (GCC) 4.2.4
[binutils]
GNU ld (Linux/GNU Binutils) 2.19.50.0.1.20081007
[autoconf]
autoconf (GNU Autoconf) 2.63
[automake]
automake (GNU automake) 1.10.1
[libtool]
ltmain.sh (GNU libtool) 1.5.26 (1.1220.2.492 2008/01/30 06:40:56)
next prev parent reply other threads:[~2008-11-20 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 2:56 [ANNOUNCE] udev 133 release Kay Sievers
2008-11-20 21:23 ` Gabor Z. Papp [this message]
2008-11-20 22:08 ` Gabor Z. Papp
2008-11-21 3:20 ` 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=x6tza2m6ru@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).