From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13226] New: external toolchain helper deletes libs if link doesn't exist
Date: Wed, 23 Sep 2020 12:45:47 +0000 [thread overview]
Message-ID: <bug-13226-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=13226
Bug ID: 13226
Summary: external toolchain helper deletes libs if link doesn't
exist
Product: buildroot
Version: 2020.08
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: protectivedad at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
The function copy_toolchain_lib_root in helpers.mk never checks to see if
LIBPATH actually exists. If it doesn't say due to the readlink -f it processes
a blank LIBPATH which deletes items in the library that have been already
copied.
A change to the while true to test for LIBPATH != "" will fix this.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-09-23 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 12:45 bugzilla at busybox.net [this message]
2024-06-15 14:55 ` [Buildroot] [Bug 13226] external toolchain helper deletes libs if link doesn't exist 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-13226-163@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