From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Which package for bluetooth management?
Date: Sun, 8 May 2016 07:52:40 +0200 [thread overview]
Message-ID: <20160508075240.142f5f78@free-electrons.com> (raw)
In-Reply-To: <e3cfa132-94c0-2b3d-7593-3286bab1e535@mind.be>
Hello,
On Sun, 8 May 2016 01:41:37 +0200, Arnout Vandecappelle wrote:
> > I've just seen bluez5 requires glibc or musl toolchain.
> > I tried to rebuild all with glibc (instead of uClibc) but the RPi3 refuses to
> > boot due to a kernel panic.
>
> Please use a serial port for debugging: the screenshot isn't really readable,
> and the interesting part has probably scrolled off-screen.
>
> However, it's extremely unlikely that changing uClibc to glibc would cause a
> kernel panic, because the kernel isn't using libc. So you have probably
> inadvertedly changed something else as well.
If you look at the kernel panic from the screenshot (I was able to read
it), it says that init was killed, i.e that the kernel couldn't run it
init. So uClibc vs. glibc could definitely make a difference here.
Marco: could you upload online the tarball image of your root
filesystem, so that we can have a look?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-08 5:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 20:55 [Buildroot] Which package for bluetooth management? Marco Trapanese
2016-05-04 22:40 ` Arnout Vandecappelle
2016-05-05 6:41 ` Marco Trapanese
2016-05-05 7:54 ` Marco Trapanese
2016-05-05 12:25 ` Thomas Petazzoni
2016-05-05 12:29 ` Marco Trapanese
2016-05-05 21:29 ` Marco Trapanese
2016-05-05 21:37 ` Thomas Petazzoni
2016-05-05 21:47 ` Marco Trapanese
2016-05-07 7:32 ` Marco Trapanese
2016-05-07 23:41 ` Arnout Vandecappelle
2016-05-08 5:52 ` Thomas Petazzoni [this message]
2016-05-08 9:09 ` Marco Trapanese
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=20160508075240.142f5f78@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