Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] bump udev and clean up
Date: Wed, 27 Jul 2011 09:34:55 +0200	[thread overview]
Message-ID: <871uxcuqg0.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <CALR4fEK2r2pL6X09pVUG970PUHxY+a52dvNdjjfVaoGLRnn3Mw@mail.gmail.com> (Diego Iastrubni's message of "Tue, 26 Jul 2011 19:00:50 +0300")

>>>>> "Diego" == Diego Iastrubni <diegoiast@gmail.com> writes:

Hi,

 Diego> My setup does not build now:
 Diego> extras/input_id/input_id.c: In function 'test_key':
 Diego> extras/input_id/input_id.c:173: error: 'BTN_TRIGGER_HAPPY' undeclared
 Diego> (first use in this function)
 Diego> extras/input_id/input_id.c:173: error: (Each undeclared identifier is
 Diego> reported only once
 Diego> extras/input_id/input_id.c:173: error: for each function it appears in.)
 Diego> make[3]: *** [extras/input_id/input_id.o] Error 1
 Diego> make[2]: *** [all-recursive] Error 1
 Diego> make[1]: *** [all] Error 2
 Diego> make[1]: Leaving directory `/home/diego/src/buildroot/output/build/udev-172'
 Diego> make: *** [/home/diego/src/buildroot/output/build/udev-172/.stamp_built] Error 2
 Diego> This new udev version needs a kernel>=2.6.33 and my toolchain (?)

Yes, BTN_TRIGGER_HAPPY was indeed only added in 2.6.34-rc1.

Diego> comes with headers of 2.6.32. I am compiling for ARM using
 Diego> codesourcery 2010q1 (I normally use a "custom" setup, but using the
 Diego> one in buildroot fails). Using?2011.03 does work.

What exactly fails with the internal toolchain?

 Diego> How do I convince the toolchain to use a newer kernel headers?

You cannot, kernel headers are part of the toolchain. Consider moving to
a newer toolchain and/or disable UDEV_EXTRAS.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2011-07-27  7:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-22 14:45 [Buildroot] [PATCH 0/3] bump udev and clean up Yegor Yefremov
2011-07-22 14:51 ` [Buildroot] [PATCH 1/3] " Yegor Yefremov
2011-07-22 14:53   ` [Buildroot] [PATCH 2/3] util-linux: convert to autotarget and bump to 2.19.1 Yegor Yefremov
2011-07-22 14:58     ` [Buildroot] [PATCH 3/3] usbmount fixes Yegor Yefremov
2011-07-27 19:13       ` Peter Korsgaard
2011-07-27 19:36         ` Yegor Yefremov
2011-07-27 19:54       ` Peter Korsgaard
2011-07-28  7:08         ` Yegor Yefremov
2011-07-27  7:43     ` [Buildroot] [PATCH 2/3] util-linux: convert to autotarget and bump to 2.19.1 Peter Korsgaard
2011-07-25 22:03   ` [Buildroot] [PATCH 1/3] bump udev and clean up Peter Korsgaard
2011-07-26  7:07     ` Yegor Yefremov
2011-07-26 16:00       ` Diego Iastrubni
2011-07-27  7:34         ` Peter Korsgaard [this message]
2011-07-27  7:51           ` Thomas Petazzoni
     [not found]           ` <CALR4fEKGFH5tq-25=j3DW-CVD5Uc-QxUeLoec-JLwSxNUhQw-w@mail.gmail.com>
     [not found]             ` <87sjpst92p.fsf@macbook.be.48ers.dk>
     [not found]               ` <CALR4fEKxDB+xH1_X+0xY9KWQXAz_g6zbrQHqzOB81J2jpOcnOg@mail.gmail.com>
2011-07-27 12:53                 ` Diego Iastrubni
2011-08-03 12:37                   ` Diego Iastrubni
2011-08-03 13:41                     ` Yegor Yefremov
2011-08-03 13:51                       ` Diego Iastrubni

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=871uxcuqg0.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox