From: Ilya Kuzmich <ilya.kuzmich@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] toolchain-external: improve musl external check
Date: Mon, 3 Apr 2017 18:25:20 +0300 [thread overview]
Message-ID: <20170403152520.GF4311@uxa> (raw)
In-Reply-To: <20170326214104.68285bca@free-electrons.com>
Turns out this is not an end to the story.
TOOLCHAIN_EXTERNAL_MUSL_LD_LINK @ pkg-toolchain-external.mk assumes that
there is a /lib/libc.so. This is not a case for ct-ng musl toolchain.
Ct-ng does this: sysroot/lib/ld-musl-armhf.so.1 -> ../usr/lib/libc.so
How do i fix this?
I've poked around pkg-toolchain-external.mk, but to no avail.
On 26/03, Thomas Petazzoni wrote:
> Hello,
>
> On Mon, 20 Mar 2017 08:56:10 +0300, Ilya Kuzmich wrote:
> > Test whether musl used or not: compile minimal C program and check if
> > interpreter contains /lib/ld-musl.
> >
> > Signed-off-by: Ilya Kuzmich <ilya.kuzmich@gmail.com>
> > ---
> > toolchain/helpers.mk | 13 +++++++++----
> > toolchain/toolchain-external/pkg-toolchain-external.mk | 4 +++-
> > 2 files changed, 12 insertions(+), 5 deletions(-)
>
> Applied to master, thanks. However, I had to make a preliminary fix
> because TOOLCHAIN_EXTERNAL_READELF had a wrong value when Buildroot
> external toolchains were used.
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
prev parent reply other threads:[~2017-04-03 15:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 5:56 [Buildroot] [PATCH 1/1] toolchain-external: improve musl external check Ilya Kuzmich
2017-03-21 22:18 ` Thomas Petazzoni
2017-03-22 8:06 ` Ilya Kuzmich
2017-03-22 8:08 ` Thomas Petazzoni
2017-03-26 19:41 ` Thomas Petazzoni
2017-04-03 15:25 ` Ilya Kuzmich [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=20170403152520.GF4311@uxa \
--to=ilya.kuzmich@gmail.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