Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] toolchain/external: fix installing libs to target (branch yem-ext-toolchain-fixes)
Date: Sun, 29 May 2016 17:17:48 +0200	[thread overview]
Message-ID: <cover.1464534979.git.yann.morin.1998@free.fr> (raw)

Hello All!

This series is a proposal to fix a regresion in the way we copy the
libraries from an external toolchain to our target directory.

The issue at stake here is that, when a custom, local toolchain is used,
that has lib{32,64} symlinks to lib/ , we would copy too much into the
target directory.

I'm not entirely sure about the first patch; it might be dropped, as it
is not required to fix the reported problem.

The real fix is the second patch.

See the individual commits for explanations.

Regards,
Yann E. MORIN.


The following changes since commit 02302d21536b9c19cd87733f4eb1bd62065416bb

  core/pkg-kconfig: pass host PKG_CONFIG_PATH env var (2016-05-28 19:46:47 +0200)


are available in the git repository at:

  https://git.busybox.net/~ymorin/git/buildroot

for you to fetch changes up to 16dd334fb29148489afa344c652208a4c512f445

  toolchain/helper: don't follow symlinks when copying libs to target (2016-05-29 17:15:41 +0200)


----------------------------------------------------------------
Yann E. MORIN (2):
      toolchain/external: fix arch-subdir
      toolchain/helper: don't follow symlinks when copying libs to target

 toolchain/helpers.mk                               | 2 +-
 toolchain/toolchain-external/toolchain-external.mk | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

             reply	other threads:[~2016-05-29 15:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-29 15:17 Yann E. MORIN [this message]
2016-05-29 15:17 ` [Buildroot] [PATCH 1/2] toolchain/external: fix arch-subdir Yann E. MORIN
2016-05-30 21:01   ` Arnout Vandecappelle
2016-05-30 21:53     ` Yann E. MORIN
2016-05-29 15:17 ` [Buildroot] [PATCH 2/2] toolchain/helper: don't follow symlinks when copying libs to target Yann E. MORIN
2016-05-29 18:54   ` Thomas De Schampheleire
2016-05-29 21:12     ` Yann E. MORIN
2016-05-29 22:33       ` Arnout Vandecappelle
2016-05-30  6:58         ` Thomas De Schampheleire
2016-05-30  7:03           ` Peter Korsgaard
2016-05-30 20:06             ` Arnout Vandecappelle
2016-05-30 20:53               ` Peter Korsgaard
2016-05-30 15:53         ` Yann E. MORIN

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=cover.1464534979.git.yann.morin.1998@free.fr \
    --to=yann.morin.1998@free.fr \
    --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