From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevd failt to compile!
Date: Tue, 12 Jul 2005 03:02:11 +0000 [thread overview]
Message-ID: <20050712030211.GA1421@kroah.com> (raw)
In-Reply-To: <27626.70.80.182.196.1120508402.squirrel@webmail.privalodc.com>
On Mon, Jul 11, 2005 at 05:39:35PM -0300, Fr?d?ric L. W. Meunier wrote:
> On Mon, 4 Jul 2005 gmourani@privalodc.com wrote:
>
> >Hello,
> >
> >I'm trying to compile latest version of udev (version 060) and it fail
> >with the following error messages:
> >
> >Compiling udevd.c:
> >[ERROR]
> > gcc -Wall -fno-builtin -Wchar-subscripts -Wpointer-arith
> >-Wstrict-prototypes
> > -Wsign-compare -Wno-pointer-sign -Wdeclaration-after-statement -pipe
> >-D_GNU_S
> > OURCE -I/usr/src/openna/BUILD/udev-060/libsysfs/sysfs
> >-I/usr/src/openna/BUILD
> > /udev-060/libsysfs -DUSE_LOG -Os -fomit-frame-pointer -Wshadow
> >-Wstrict-proto
> > 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
> > udevd.c: In function 'init_uevent_netlink_sock':
> > udevd.c:755: error: storage size of 'snl' isn't known
> > udevd.c:758: error: invalid application of 'sizeof' to incomplete type
> >'struc
> > t sockaddr_nl'
> > udevd.c:770: error: invalid application of 'sizeof' to incomplete type
> >'struc
> > t sockaddr_nl'
> > udevd.c:755: warning: unused variable 'snl'
> >make: *** [udevd.o] Error 1
> >
> >udev 058 compiled successfuly without problem or error, does some know
> >what this happen with latest stable realese of udev 060??
>
> The same for me. Using kernel-headers-2.4.31-i386-1 from
> Slackware-current. Nothing broken on my system.
Use a kernel-headers from a 2.6 kernel please.
Also, does this still happen on 062?
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
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-12 3:02 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
2005-07-11 20:39 ` Frédéric L. W. Meunier
2005-07-12 3:02 ` Greg KH [this message]
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=20050712030211.GA1421@kroah.com \
--to=greg@kroah.com \
--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).