Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <jkrause@posteo.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] toolchain/helpers.mk: fix check-musl
Date: Mon, 08 Dec 2014 22:17:03 +0100	[thread overview]
Message-ID: <1418073423.2353.13.camel@posteo.de> (raw)
In-Reply-To: <20141208203200.4ca75210@free-electrons.com>

On Mo, 2014-12-08 at 20:32 +0100, Thomas Petazzoni wrote:
> Dear J?rg Krause,
> 
> On Thu,  4 Dec 2014 00:13:59 +0100, J?rg Krause wrote:
> > check_musl works fine for the external musl 1.1.1 toolchain which is downloaded
> > and installed, but fails for a musl toolchain which, in a first step is build
> > by the internal toolchain backend of Buildroot, and in a second step is copied
> > to an external directory and imported as an custom external toolchain (in a new
> > configuration).
> > 
> > In case of the downloaded musl 1.1.1 toolchain the libc.so and libm.a files
> > reside in the sysroot/lib directory and sysroot/usr/lib is a symlink to
> > sysroot/lib.
> > 
> > In case of the custom musl toolchain build by Buildroot the files reside in
> > sysroot/usr/lib which is not a symlink.
> 
> Actually, I am not sure this is the best fix we could do. Having the C
> library installed in /usr/lib in the sysroot is a bit weird, and I
> believe we should rather fix the Buildroot musl package to ensure that
> the C library gets installed in /lib instead.
> 
> Do you want to have a look into this?

I'm not a toolchain expert, but I will have a look at it.

  reply	other threads:[~2014-12-08 21:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03 23:13 [Buildroot] [PATCH 1/1] toolchain/helpers.mk: fix check-musl Jörg Krause
2014-12-08 19:32 ` Thomas Petazzoni
2014-12-08 21:17   ` Jörg Krause [this message]
2014-12-08 21:21     ` Thomas Petazzoni
2014-12-09  1:22       ` Jörg Krause

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=1418073423.2353.13.camel@posteo.de \
    --to=jkrause@posteo.de \
    --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