public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: John David Anglin <danglin@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] support: Build with exceptions and asynchronous unwind tables [BZ #30587]
Date: Sat,  1 Jul 2023 13:30:50 +0000 (GMT)	[thread overview]
Message-ID: <20230701133050.31D733858D35@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=1d5024f4f052c12e404d42d3b5bfe9c3e9fd27c4

commit 1d5024f4f052c12e404d42d3b5bfe9c3e9fd27c4
Author: John David Anglin <danglin@gcc.gnu.org>
Date:   Sat Jul 1 13:29:53 2023 +0000

    support: Build with exceptions and asynchronous unwind tables [BZ #30587]
    
    Changing tst-cleanup4.c to use xread instead of read caused
    the nptl/tst-cleanupx4 test to fail.  The routines in libsupport.a
    need to be built with exception handling and asynchronous unwind
    table support.
    
    v2: Use "CFLAGS-.oS" instead of "override CFLAGS".

Diff:
---
 support/Makefile | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/support/Makefile b/support/Makefile
index c81e3c928c..917a858bd1 100644
--- a/support/Makefile
+++ b/support/Makefile
@@ -239,6 +239,9 @@ CFLAGS-support_paths.c = \
 		-DCOMPLOCALEDIR_PATH=\"$(complocaledir)\" \
 		-DSYSCONFDIR_PATH=\"$(sysconfdir)\"
 
+# Build with exception handling and asynchronous unwind table support.
+CFLAGS-.oS += -fexceptions -fasynchronous-unwind-tables
+
 # In support_timespec_check_in_range we may be passed a very tight
 # range for which we should produce a correct result for expected
 # being within the observed range.  The code uses double internally

                 reply	other threads:[~2023-07-01 13:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230701133050.31D733858D35@sourceware.org \
    --to=danglin@sourceware.org \
    --cc=glibc-cvs@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).