From: "H.J. Lu" <hjl.tools@gmail.com>
To: libc-alpha@sourceware.org
Cc: fweimer@redhat.com
Subject: [PATCH v2 0/2] Opt-out static C++ link check and tests
Date: Sat, 25 May 2024 05:26:39 -0700 [thread overview]
Message-ID: <20240525122641.3154365-1-hjl.tools@gmail.com> (raw)
The current glibc build and test will fail if static C++ link doesn't
work. There are cases where static C++ link is hard to supported:
1. Building i686 glibc with GCC 6.4 on Fedora 40 failed since the C++
header files couldn't be found which was caused by the static C++ link
check failure due to missing __divmoddi4 which was referenced in i686
libc.a and added to GCC 7.
2. Glibc test won't finish because static C++ tests fail when the C++
toolchain doesn't have necessary static C++ libraries which may not be
easily installed.
Add --disable-static-c++-link-check configure option to disable the static
C++ link check. Add --disable-static-c++-tests option to skip the static
C++ tests which also implies --disable-static-c++-link-check.
H.J. Lu (2):
Add --disable-static-c++-link-check option [BZ #31412]
Add --disable-static-c++-tests option [BZ #31797]
INSTALL | 17 +++++++++++++++++
configure | 44 ++++++++++++++++++++++++++++++++++++--------
configure.ac | 35 +++++++++++++++++++++++++----------
manual/install.texi | 16 ++++++++++++++++
nptl/Makefile | 3 +++
5 files changed, 97 insertions(+), 18 deletions(-)
--
2.45.1
next reply other threads:[~2024-05-25 12:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-25 12:26 H.J. Lu [this message]
2024-05-25 12:26 ` [PATCH v2 1/2] Add --disable-static-c++-link-check option [BZ #31412] H.J. Lu
2024-06-20 18:22 ` Carlos O'Donell
2024-05-25 12:26 ` [PATCH v2 2/2] Add --disable-static-c++-tests option [BZ #31797] H.J. Lu
2024-06-20 18:22 ` Carlos O'Donell
2024-06-20 18:23 ` [PATCH v2 0/2] Opt-out static C++ link check and tests Carlos O'Donell
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=20240525122641.3154365-1-hjl.tools@gmail.com \
--to=hjl.tools@gmail.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).