All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] inotify-tools: Add new package
Date: Tue, 26 Jul 2011 15:03:54 +0200	[thread overview]
Message-ID: <87hb6942it.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1311630415-633-1-git-send-email-mike@mikebwilliams.com> (Mike Williams's message of "Mon, 25 Jul 2011 17:46:55 -0400")

>>>>> "Mike" == Mike Williams <mike@mikebwilliams.com> writes:

 Mike> Adds support for inotify-tools, which are useful for scripting the
 Mike> Linux inotify API.

Thanks, committed with minor tweaks (see below)

 Mike> +++ b/package/inotify-tools/Config.in
 Mike> @@ -0,0 +1,10 @@
 Mike> +config BR2_PACKAGE_INOTIFY_TOOLS
 Mike> +	bool "inotify-tools"
 Mike> +	help
 Mike> +	  inotify-tools is a C library and a set of command-line
 Mike> +	  programs for Linux providing a simple interface to inotify.
 Mike> +	  These programs can be used to monitor and act upon
 Mike> +	  filesystem events. Provides the 'inotifywait' and 'inotifywatch'
 Mike> +		binaries.

Here the build fails with:

inotifytools.c: In function 'inotifytools_watch_recursively_with_exclude':
inotifytools.c:1312: error: storage size of 'my_stat' isn't known
inotifytools.c:1319: warning: implicit declaration of function 'lstat64'
inotifytools.c: In function 'isdir':
inotifytools.c:1598: error: storage size of 'my_stat' isn't known
make[5]: *** [inotifytools.lo] Error 1

So you need largefile support in the toolchain, and the package should
depend on BR2_LARGEFILE.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2011-07-26 13:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25 21:46 [Buildroot] [PATCH] inotify-tools: Add new package Mike Williams
2011-07-26 13:03 ` Peter Korsgaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-07-25 20:38 Mike Williams
2011-07-25 20:54 ` Peter Korsgaard
     [not found]   ` <CANPyyuOjm8U6osYRJWZKwWpRFJFQ1GXGjMJEA4TgG3oYH9MZGg@mail.gmail.com>
2011-07-25 21:11     ` Mike Williams

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=87hb6942it.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.