From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] busybox error
Date: Mon, 7 Nov 2016 23:03:02 +0100 [thread overview]
Message-ID: <20161107230302.69f0ef4b@free-electrons.com> (raw)
In-Reply-To: <d563d924-cd16-f433-f1f4-e3f37cfef008@mind.be>
Hello,
On Mon, 7 Nov 2016 22:58:01 +0100, Arnout Vandecappelle wrote:
> You have done some very serious hacking, so don't be surprised if things don't
> work.
>
> busybox runlevel can only be enabled when busybox FEATURE_UTMP is enabled.
> However, Buildroot will explicitly disable that option when musl is used as libc
> because musl doesn't provide utmpxname (and another one too I think).
>
> I don't know how you managed to break this, but it must be by manually copying
> some files into the build directory. If you do something like that, you're on
> your own. It's like pulling a screw out of the engine of your car and going to
> your car dealer complaining that something doesn't work.
>
> Now, I could be mistaken, so if you can reproduce the issue after doing 'make
> clean; make', please provide your buildroot .config and busybox .config (if it
> was customized).
FWIW, Siva provided me off-list (or rather without Cc'ing the list) his
Buildroot .config file, which selects the glibc C library. But his
build log indeed indicates a toolchain built the musl C library.
Which hints very clearly that Siva didn't do a "make clean all" after
changing the toolchain configuration.
Siva: please read
https://buildroot.org/downloads/manual/manual.html#full-rebuild.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-11-07 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 9:04 [Buildroot] busybox error Siva Prakash Reddy Nareddy
2016-11-07 9:31 ` Thomas Petazzoni
2016-11-07 21:58 ` Arnout Vandecappelle
2016-11-07 22:03 ` 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=20161107230302.69f0ef4b@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