From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] problem when using build cache ?
Date: Tue, 31 Jan 2012 17:26:06 +0100 [thread overview]
Message-ID: <20120131172606.6b123f1d@skate> (raw)
In-Reply-To: <9C7AEB06A00A49B5BC4F3D164ABB579E@JohanW7>
Hello,
Le Tue, 31 Jan 2012 17:10:46 +0100,
"Sagaert Johan" <sagaert.johan@skynet.be> a ?crit :
> The udev version in 2011.11 (v1.73) does not generate the /dev/pts nodes and as result there is no devpts in the mounts.
I guess you're talking about version 173 of udev, there is no such
thing as 1.73. If you use udev, then your kernel must have
CONFIG_DEVTMPFS and CONFIG_DEVTMPFS_MOUNT enabled. If you let Buildroot
build your kernel, then Buildroot will automatically ensure that your
kernel is configured with those two options enabled. If you build your
kernel manually outside of Buildroot, then you must enable those
options, otherwise udev will not work.
I guess this is where your problem is: check your kernel configuration.
> I noticed udev 1.14 does not build when the build ccache is ON.
Honestly, we don't really care about udev 114 since the current
Buildroot version contains udev 173, and this one appears to build
properly with ccache enabled.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-01-31 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 16:10 [Buildroot] problem when using build cache ? Sagaert Johan
2012-01-31 16:23 ` Peter Korsgaard
2012-01-31 19:38 ` Sagaert Johan
2012-01-31 22:20 ` Peter Korsgaard
2012-01-31 16:26 ` Thomas Petazzoni [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=20120131172606.6b123f1d@skate \
--to=thomas.petazzoni@free-electrons.com \
--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