From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15156] New: Excess library installation to ARM64 target.
Date: Mon, 28 Nov 2022 08:47:25 +0000 [thread overview]
Message-ID: <bug-15156-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15156
Bug ID: 15156
Summary: Excess library installation to ARM64 target.
Product: buildroot
Version: 2022.08.2
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: Alexey.Kazantsev@kaspersky.com
CC: buildroot@uclibc.org
Target Milestone: ---
Hello!
Is have noticed, that in the image built with qemu_aarch64_virt_defconfig
config some libraries not required by the image binaries, i.e.: libgcc_s.so.1,
libgcc_s.so, libatomic.so .
These libraries are listed in the TOOLCHAIN_EXTERNAL_LIBS variable in the
toolchain/toolchain-external/pkg-toolchain-external.mk file.
As I can see, they are not installed in the same way as other libraries,
however, they defenitelly excess in the built rootfs.
Is it possible adding build stage to clean these unused libraries?
This issue exists in 2022.11-rc2 also.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-11-28 8:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 8:47 bugzilla [this message]
2022-11-28 8:48 ` [Buildroot] [Bug 15156] Excess libraries are installed to the ARM64 QEMU target bugzilla
2022-12-05 10:00 ` bugzilla
2024-06-15 15:04 ` 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-15156-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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