public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libbacktrace/111315] libstdc++ stacktrace testsuite failures with --enable-default-pie Date: Mon, 06 Nov 2023 23:11:59 +0000 [thread overview] Message-ID: <bug-111315-4-7rgFjFvYBS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111315-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111315 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Ian Lance Taylor <ian@gcc.gnu.org>: https://gcc.gnu.org/g:2b64e4a54042fb8f75f1c1429eb1c13afb9fa118 commit r14-5173-g2b64e4a54042fb8f75f1c1429eb1c13afb9fa118 Author: Ian Lance Taylor <iant@golang.org> Date: Mon Nov 6 15:09:18 2023 -0800 libstdc++: use -D_GNU_SOURCE when building libbacktrace PR libbacktrace/111315 PR libbacktrace/112263 * acinclude.m4: Set -D_GNU_SOURCE in BACKTRACE_CPPFLAGS and when grepping link.h for dl_iterate_phdr. * configure: Regenerate.
next prev parent reply other threads:[~2023-11-06 23:11 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-07 3:49 [Bug libstdc++/111315] New: " rimvydas.jas at gmail dot com 2023-09-07 3:58 ` [Bug libstdc++/111315] " pinskia at gcc dot gnu.org 2023-09-07 10:34 ` xry111 at gcc dot gnu.org 2023-09-07 10:38 ` xry111 at gcc dot gnu.org 2023-10-31 20:06 ` [Bug libbacktrace/111315] " pinskia at gcc dot gnu.org 2023-11-03 10:03 ` xry111 at gcc dot gnu.org 2023-11-03 16:26 ` rimvydas.jas at gmail dot com 2023-11-03 16:32 ` redi at gcc dot gnu.org 2023-11-06 23:11 ` cvs-commit at gcc dot gnu.org [this message] 2023-11-06 23:12 ` cvs-commit at gcc dot gnu.org 2023-11-06 23:13 ` cvs-commit at gcc dot gnu.org
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-111315-4-7rgFjFvYBS@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).