From: Ilya Kuzmich <ilya.kuzmich@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] toolchain-external: improve musl external check
Date: Wed, 22 Mar 2017 11:06:51 +0300 [thread overview]
Message-ID: <20170322080651.GC29607@uxa> (raw)
In-Reply-To: <20170321231856.014bc6a7@free-electrons.com>
Current check fails on crosstool-ng musl toolchain,
ctng puts libc.so at sysroot/usr/lib/, not sysroot/lib
On 21/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>
>
> This doesn't look bad, but what is the motivation behind the change? Is
> the current check not working for you?
>
> Thanks!
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
next prev parent reply other threads:[~2017-03-22 8:06 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 [this message]
2017-03-22 8:08 ` Thomas Petazzoni
2017-03-26 19:41 ` Thomas Petazzoni
2017-04-03 15:25 ` Ilya Kuzmich
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=20170322080651.GC29607@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