From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9846] musl libc not installed correctly in target folder
Date: Sun, 07 May 2017 19:34:54 +0000 [thread overview]
Message-ID: <bug-9846-163-axMbp7PuyX@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9846-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9846
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|NEW |RESOLVED
--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Thanks for your report. Unfortunately, I'm not able to reproduce. The musl
system produced by your defconfig looks OK to me:
$ ls -l target/lib/libc.so
-rwxr-xr-x 1 test test 587296 May 7 15:29 target/lib/libc.so
And it boots just fine (tested under Qemu):
Welcome to TEST
test login:
Welcome to TEST
test login:
So, a few options:
1. Something has been fixed since then, but I don't recall any fix related to
this being applied recently.
2. Something is different on your build machine.
3. You did not clean up the build completely.
I'll mark the bug as WORKSFORME for now. If you manage to reproduce again with
the latest Buildroot, could you try to preview a simpler defconfig that
exhibits the issue so that we can try to narrow down the issue ?
Keeping the full build log would also be useful.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2017-05-07 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 20:03 [Buildroot] [Bug 9846] New: musl libc not installed correctly in target folder bugzilla at busybox.net
2017-05-07 19:34 ` bugzilla at busybox.net [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=bug-9846-163-axMbp7PuyX@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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