From: belle <belle.shi@yy-inc.com>
To: linux-hotplug@vger.kernel.org
Subject: how to resolve:udev-141/udev/udev-watch.c:157: undefined reference
Date: Mon, 25 Jan 2010 09:42:56 +0000 [thread overview]
Message-ID: <1264412576.3730.13.camel@shili-desktop> (raw)
dear all:
i am doing the cross-complile to the udev,and the version is 141,the
target platform is mips, but i find the error:
udev-watch.o: In function `udev_watch_end':
/home/shili/tar/udev-141/udev/udev-watch.c:157: undefined reference to
`inotify_rm_watch'
collect2: ld returned 1 exit status
i don't know which file provide the func "inotify_rm_watch", so i don't
know i should compile which file to solve the problem.
any help will be appreciate, thanks for advance.
------------------------------------------------
and there is another questions:
i used the udevd complied by other people, but i find my program
can't receive the udev event, but i use the command udevadm --monitor,i
can see there are lots of udev events,i add my rules 90-nmd.rules to the
the dir /etc/udev/rules.d/ and restart the udevd --daemon,but i still
can't get the udev event, my program is ok on the x86 platfrom.
so i guess if the udevd did't parse my rules file, so i use the
command:"udevd --daemon --debug-trace --debug" to see the files which
parsed by udevd, but it only shows
udevd --daemon --debug-trace --debug
udevd[912]: lookup_group: specified group 'lp' unknown
udevd[912]: lookup_group: specified group 'lp' unknown
udevd[912]: lookup_group: specified group 'lp' unknown
udevd[912]: lookup_group: specified group 'lp' unknown
udevd[912]: lookup_group: specified group 'lp' unknown
udevd[912]: lookup_group: specified group 'floppy' unknown
also: any help will be appreciate, thanks for advance.
reply other threads:[~2010-01-25 9:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1264412576.3730.13.camel@shili-desktop \
--to=belle.shi@yy-inc.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