From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevd failt to compile!
Date: Mon, 04 Jul 2005 20:30:53 +0000 [thread overview]
Message-ID: <20050704203053.GA15003@vrfy.org> (raw)
In-Reply-To: <27626.70.80.182.196.1120508402.squirrel@webmail.privalodc.com>
On Mon, Jul 04, 2005 at 04:20:02PM -0400, gmourani@privalodc.com wrote:
> Hello,
>
> I'm trying to compile latest version of udev (version 060) and it fail
> with the following error messages:
>
> types -Wmissing-prototypes -Wmissing-declarations -c -o udevd.o udevd.c
> In file included from udevd.c:41:
> /usr/include/linux/netlink.h:22: error: parse error before '__u32'
> /usr/include/linux/netlink.h:28: error: parse error before '__u32'
> /usr/include/linux/netlink.h:30: error: parse error before 'nlmsg_flags'
> /usr/include/linux/netlink.h:31: error: parse error before 'nlmsg_seq'
> /usr/include/linux/netlink.h:32: error: parse error before 'nlmsg_pid'
> /usr/include/linux/netlink.h:82: error: field 'msg' has incomplete type
Seems you messed around your glibc-kernel-headers. Did you copy the
linux-kernel includes to /usr/include/linux?
Kay
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-07-04 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-04 20:20 udevd failt to compile! gmourani
2005-07-04 20:24 ` Michael Buesch
2005-07-04 20:30 ` Kay Sievers [this message]
2005-07-11 20:39 ` Frédéric L. W. Meunier
2005-07-12 3:02 ` Greg KH
2005-07-12 3:20 ` Frédéric L. W. Meunier
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=20050704203053.GA15003@vrfy.org \
--to=kay.sievers@vrfy.org \
--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).