From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9111] glibc 2.23: libmvec.so not copied
Date: Sat, 15 Oct 2016 15:49:31 +0000 [thread overview]
Message-ID: <bug-9111-163-udTDJX3em6@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-9111-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=9111
--- Comment #2 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
We had a discussion about this, and here is the conclusion: we will simply add
libmvec.so to the list of libraries to copy, for both the internal toolchain
backend (glibc.mk) and the external toolchain backend (toolchain-external.mk).
The function used to copy libraries from the staging directory to the target
directory already ignores libraries that don't exist, so it's not a problem to
unconditionally try to copy libmvec.so. It will be silently ignored on
systems/C libraries/architectures where it is not available.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-10-15 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 23:04 [Buildroot] [Bug 9111] New: glibc 2.23: libmvec.so not copied bugzilla at busybox.net
2016-07-30 9:16 ` [Buildroot] [Bug 9111] " bugzilla at busybox.net
2016-10-15 15:49 ` bugzilla at busybox.net [this message]
2016-10-26 21:48 ` bugzilla at busybox.net
2016-11-03 20:45 ` bugzilla at busybox.net
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-9111-163-udTDJX3em6@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.