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 17:53:25 +0200 [thread overview]
Message-ID: <50A66175.6090107@ronetix.at> (raw)
In-Reply-To: <20121116164504.6270393b@skate>
On 16/11/12 17:45, Thomas Petazzoni wrote:
> On Fri, 16 Nov 2012 16:02:50 +0100, Zoltan Gyarmati wrote:
>
>>> Thanks for the fast response but when I configure Buildroot to use
>>> external toolchain the Kernel headers option dissapear. Any other advice?
>> yes, in this case it comes from the toolchain itself, sou you have to
>> check it in the toolchain.
> If Martin is using the external toolchain backend, then he cannot check
> anything related to the kernel headers version in the menuconfig.
> External toolchains are pre-built toolchains, so Buildroot just uses
> them as-is, you have no way of changing the Buildroot version.
>
> Martin: your external toolchain is using too old kernel headers to
> build udev. So your options are:
>
> *) Use a more recent external toolchain that will have more recent
> kernel headers.
>
> *) Add a patch to udev that defines BTN_TRIGGER_HAPPY to the correct
> value when it is not already defined by kernel headers.
>
> BTW, which external toolchain are you using?
>
> Thanks,
>
> Thomas
Thanks, Thomas! I use arm-oe-gnueabi- toolchain. Can you explain how to
add a patch to udev to correct the problem?
I'm afraid of using another toolchain because I compile the Kernel and
the rootfs separately.
prev parent reply other threads:[~2012-11-16 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 14:41 [Buildroot] Buildroot fail to build when configure for dev managment: dynamically with udev Martin Peevski
2012-11-16 14:54 ` 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 [this message]
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=50A66175.6090107@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox