From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Busybox build fails on raspberrypi defconfig
Date: Wed, 17 Jun 2015 16:41:34 +0200 [thread overview]
Message-ID: <20150617164134.01411faf@free-electrons.com> (raw)
In-Reply-To: <CAJtjsKa9Osr3VjF6jBysCFPEKhh4c8HAHVP7FfVj07_N_B1FMQ@mail.gmail.com>
Dear Johan Oudinet,
On Wed, 17 Jun 2015 16:02:10 +0200, Johan Oudinet wrote:
> On Wed, Jun 17, 2015 at 3:27 PM, Johan Oudinet <johan.oudinet@gmail.com> wrote:
> > And busybox build fails with the following error:
> > include/libbb.h:87:19: fatal error: utmp.h: No such file or directory
> > # include <utmp.h>
> > ^
>
> Reverting from uClibc-ng to uClibc-0.9.33 fixes this error.
This seems weird, since UTMP is enabled in our uClibc-ng configuration:
$ grep UTMP *.config
uClibc-0.9.33.config:UCLIBC_HAS_UTMPX=y
uClibc-ng.config:UCLIBC_HAS_UTMP=y
uClibc-ng.config:UCLIBC_HAS_UTMPX=y
uClibc-snapshot.config:UCLIBC_HAS_UTMP=y
uClibc-snapshot.config:UCLIBC_HAS_UTMPX=y
And it's really UCLIBC_HAS_UTMP that controls whether utmp.h is
installed or not:
HEADERS_RM-$(UCLIBC_HAS_UTMP) += bits/utmp.h utmp.h
HEADERS_RM-$(UCLIBC_HAS_UTMPX) += bits/utmpx.h utmpx.h
Are you sure you did a full rebuild from scratch, and you didn't select
uClibc-ng but using package/uclibc/uClibc-0.9.33.config as the
configuration file ? That could explain the problem, because the
UCLIBC_HAS_UTMP option didn't exist in uClibc-0.9.33.config, so if you
use that config file with uClibc-ng, UTMP support will be disabled.
Can you double check this?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-06-17 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 13:27 [Buildroot] Busybox build fails on raspberrypi defconfig Johan Oudinet
2015-06-17 14:02 ` Johan Oudinet
2015-06-17 14:41 ` Thomas Petazzoni [this message]
2015-06-18 8:54 ` Johan Oudinet
2015-06-18 9:02 ` Thomas Petazzoni
2015-06-18 16:08 ` Arnout Vandecappelle
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=20150617164134.01411faf@free-electrons.com \
--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