From: "Gabor Z. Papp" <gzp@papp.hu>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 126 release
Date: Fri, 08 Aug 2008 11:33:34 +0000 [thread overview]
Message-ID: <x63alfg2r5@gzp> (raw)
In-Reply-To: <1217832786.4223.2.camel@linux.site>
* "Gabor Z. Papp" <gzp@papp.hu>:
| | > Linux gzp1 2.4.36.6-gzp1 #1 SMP Sat Jun 7 08:43:14 CEST 2008 i686 GNU/Linux
| | Udev depends on a 2.6 kernel. :) The udev build depends on
| | kernel-headers, which contain the features udev uses.
| okay. v125 built fine on 2.4
Building on 2.6.26.2:
make all-recursive
make[1]: Entering directory `/mnt/harddisk/home/gzp/src/udev-126'
Making all in udev
make[2]: Entering directory `/mnt/harddisk/home/gzp/src/udev-126/udev'
gcc -DHAVE_CONFIG_H -I. -I.. -DSYSCONFDIR=\""/usr/etc"\" -DUDEV_PREFIX=\""/usr"\" -g -O2 -MT udevd.o -MD -MP -MF .deps/udevd.Tpo -c -o udevd.o udevd.c
udevd.c: In function `main':
udevd.c:1152: error: `IN_CREATE' undeclared (first use in this function)
udevd.c:1152: error: (Each undeclared identifier is reported only once
udevd.c:1152: error: for each function it appears in.)
udevd.c:1152: error: `IN_DELETE' undeclared (first use in this function)
udevd.c:1152: error: `IN_MOVE' undeclared (first use in this function)
udevd.c:1152: error: `IN_CLOSE_WRITE' undeclared (first use in this function)
make[2]: *** [udevd.o] Error 1
make[2]: Leaving directory `/mnt/harddisk/home/gzp/src/udev-126/udev'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/mnt/harddisk/home/gzp/src/udev-126'
make: *** [all] Error 2
next prev parent reply other threads:[~2008-08-08 11:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 6:53 [ANNOUNCE] udev 126 release Kay Sievers
2008-08-04 12:49 ` Karel Zak
2008-08-08 10:55 ` Gabor Z. Papp
2008-08-08 11:14 ` Kay Sievers
2008-08-08 11:14 ` Gabor Z. Papp
2008-08-08 11:33 ` Gabor Z. Papp [this message]
2008-08-08 11:53 ` Kay Sievers
2008-08-08 12:00 ` Gabor Z. Papp
2008-08-08 20:47 ` Kay Sievers
2008-08-08 21:18 ` Marco d'Itri
2008-08-09 8:58 ` Kay Sievers
2008-08-09 9:41 ` Gabor Z. Papp
2008-08-09 9:50 ` 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=x63alfg2r5@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).