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: Wed, 29 Mar 2017 16:45:51 +0000 [thread overview]
Message-ID: <bug-9771-163-SB870FegEF@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 #6 from sir.ferdek+buildroot at gmail.com ---
(In reply to Thomas Petazzoni from comment #5)
> So, are we looking at a Buildroot bug, or a Crosstool-NG bug?
Looks like this is known and ongoing development. I have found a recent
activity regarding this issue in Crostool-NG.
https://github.com/crosstool-ng/crosstool-ng/pull/639
And then, look at this commit message from 12 days ago (included in merged pull
request):
https://github.com/crosstool-ng/crosstool-ng/pull/639/commits/63b2a19de4b33f304b236850028b6c6f32ce51e2
I guess it might require both Buildroot and CT-NG to synchronize on this
issue... :D
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-03-29 16:45 UTC|newest]
Thread overview: 12+ 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 [this message]
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
2024-06-15 14:47 ` bugzilla
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-SB870FegEF@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.