From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4] Solving the musl dynamic linker issues
Date: Wed, 5 Jul 2017 12:24:34 +0200 [thread overview]
Message-ID: <20170705122434.41897a0e@windsurf> (raw)
In-Reply-To: <20170702134107.11488-1-thomas.petazzoni@free-electrons.com>
Hello,
On Sun, 2 Jul 2017 15:41:03 +0200, Thomas Petazzoni wrote:
> Thomas Petazzoni (4):
> support/testing: add tests for musl and uclibc toolchains
> toolchain/helpers.mk: re-evaluate DESTDIR in copy_toolchain_lib_root
> toolchain-external: copy ld*.so* for all C libraries
> toolchain-external: also put libgcc_s.so unconditionally in
> TOOLCHAIN_EXTERNAL_LIBS
I've applied the series, and I've added a 5th patch that removes the
ld*.so handling in copy_toolchain_sysroot, keeping only ld*.so.* to be
consistent with what TOOLCHAIN_EXTERNAL_LIBS says. This (hopefully)
addresses Thomas DS comment :-)
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-07-05 10:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-02 13:41 [Buildroot] [PATCH 0/4] Solving the musl dynamic linker issues Thomas Petazzoni
2017-07-02 13:41 ` [Buildroot] [PATCH 1/4] support/testing: add tests for musl and uclibc toolchains Thomas Petazzoni
2017-07-02 13:43 ` Thomas Petazzoni
2017-07-03 13:15 ` Arnout Vandecappelle
2017-07-02 13:41 ` [Buildroot] [PATCH 2/4] toolchain/helpers.mk: re-evaluate DESTDIR in copy_toolchain_lib_root Thomas Petazzoni
2017-07-02 13:41 ` [Buildroot] [PATCH 3/4] toolchain-external: copy ld*.so* for all C libraries Thomas Petazzoni
2017-07-02 13:49 ` Baruch Siach
2017-07-02 19:21 ` Thomas De Schampheleire
2017-07-02 21:51 ` Thomas Petazzoni
2017-07-02 13:41 ` [Buildroot] [PATCH 4/4] toolchain-external: also put libgcc_s.so unconditionally in TOOLCHAIN_EXTERNAL_LIBS Thomas Petazzoni
2017-07-05 10:24 ` Thomas Petazzoni [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=20170705122434.41897a0e@windsurf \
--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