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: Thu, 07 Jun 2018 14:07:38 +0000 [thread overview]
Message-ID: <bug-9771-163-yUqzuMrVmc@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9771-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9771
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at buildroot.uclibc |patrickdepinguin at gmail.com
|.org |
--- Comment #8 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
I tested with the latest Buildroot (which includes the changes Thomas DS was
mentioning in his comment), and indeed the separation of lib/ (for gcc
libraries) and lib64/ has the consequence that libgcc_s.so is not copied to
staging nor to target.
The proposal to include "lib" in the list of folders from the sysroot to copy
seems sensible to me, perhaps we should add "usr/lib" as well.
Thomas DS, any comment on this ?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-06-07 14:07 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
2017-03-30 9:30 ` bugzilla at busybox.net
2018-06-07 14:07 ` bugzilla at busybox.net [this message]
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-yUqzuMrVmc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox