All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9771] toolchain-external misses lib directory when copying sysroot
Date: Mon, 12 Aug 2019 18:32:22 +0000	[thread overview]
Message-ID: <bug-9771-163-D0yeLoeSRL@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9771-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=9771

--- Comment #10 from Thomas De Schampheleire <patrickdepinguin@gmail.com> ---
Sorry, it seems I never saw comment #8.

Copying the entire 'lib' from the external toolchain's sysroot into
staging/target will copy too much for some multilib toolchains, e.g. similar to
the octeon toolchain described in http://patchwork.ozlabs.org/patch/725387/ but
with 'lib/octeon2' instead of 'lib32/octeon2'. I think there are also other
toolchains where this will be a problem.

So, if the original problem is still an issue with current Buildroot and
reasonably recent toolchains, then I think a better solution should be found.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2019-08-12 18:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-22  9:23 [Buildroot] [Bug 9771] New: toolchain-external misses lib directory when copying sysroot bugzilla at busybox.net
2017-03-22 20:35 ` [Buildroot] [Bug 9771] " bugzilla at busybox.net
2017-03-28  6:44 ` bugzilla at busybox.net
2017-03-28 20:04 ` bugzilla at busybox.net
2017-03-28 20:35 ` bugzilla at busybox.net
2017-03-28 20:43 ` bugzilla at busybox.net
2017-03-29 16:45 ` bugzilla at busybox.net
2017-03-30  9:30 ` bugzilla at busybox.net
2018-06-07 14:07 ` bugzilla at busybox.net
2019-08-10 23:38 ` bugzilla at busybox.net
2019-08-12 18:32 ` bugzilla at busybox.net [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=bug-9771-163-D0yeLoeSRL@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.