All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Peevski <martin@ronetix.at>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot fail to build when configure for dev managment: dynamically with udev
Date: Fri, 16 Nov 2012 16:41:24 +0200	[thread overview]
Message-ID: <50A65094.7080202@ronetix.at> (raw)

     Hi,

     I tryed to build Buildroot with only rootfs, I have already built 
Kernel image. Use external toolchain for the building. I configure 
Buildroot for dynamically /dev managment with udev but during udev 
building I got the following errors:

src/udev-builtin-input_id.c: In function 'test_key':
src/udev-builtin-input_id.c:165: error: 'BTN_TRIGGER_HAPPY' undeclared 
(first use in this function)
src/udev-builtin-input_id.c:165: error: (Each undeclared identifier is 
reported only once
src/udev-builtin-input_id.c:165: error: for each function it appears in.)
make[4]: *** [src/udevadm-udev-builtin-input_id.o] Error 1
make[4]: *** Waiting for unfinished jobs....
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** 
[/home/martin/Desktop/sam9x5-linux-sources/rootfs/build/udev-182/.stamp_built] 
Error 2
make: *** [all] Error 2

      Can you, please, give me some advices?

             reply	other threads:[~2012-11-16 14:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16 14:41 Martin Peevski [this message]
2012-11-16 14:54 ` [Buildroot] Buildroot fail to build when configure for dev managment: dynamically with udev Zoltan Gyarmati
     [not found]   ` <50A65565.9050001@ronetix.at>
2012-11-16 15:02     ` Zoltan Gyarmati
     [not found]       ` <50A6577F.3030505@ronetix.at>
2012-11-16 15:40         ` Zoltan Gyarmati
2012-11-16 15:45       ` Thomas Petazzoni
2012-11-16 15:53         ` Martin Peevski

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=50A65094.7080202@ronetix.at \
    --to=martin@ronetix.at \
    --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.