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 libstdc++/111936] std::stacktrace cannot be used in a shared library
Date: Wed, 25 Oct 2023 10:28:44 +0000 [thread overview]
Message-ID: <bug-111936-4-9WY7urRCJU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111936-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111936
--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:
https://gcc.gnu.org/g:f32c1e1e96ffef6512ce025942b51f3967a3e7f2
commit r14-4922-gf32c1e1e96ffef6512ce025942b51f3967a3e7f2
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Tue Oct 24 16:56:30 2023 +0100
libstdc++: Build libstdc++_libbacktrace.a as PIC [PR111936]
In order for std::stacktrace to be used in a shared library, the
libbacktrace symbols need to be built with -fPIC. Add the libtool
-prefer-pic flag to the commands in src/libbacktrace/Makefile so that
the archive contains PIC objects.
libstdc++-v3/ChangeLog:
PR libstdc++/111936
* src/libbacktrace/Makefile.am: Add -prefer-pic to libtool
compile commands.
* src/libbacktrace/Makefile.in: Regenerate.
next prev parent reply other threads:[~2023-10-25 10:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 13:09 [Bug libstdc++/111936] New: " vincenzo.innocente at cern dot ch
2023-10-23 13:23 ` [Bug libstdc++/111936] " vincenzo.innocente at cern dot ch
2023-10-23 14:28 ` redi at gcc dot gnu.org
2023-10-23 14:32 ` redi at gcc dot gnu.org
2023-10-23 14:32 ` redi at gcc dot gnu.org
2023-10-23 16:13 ` redi at gcc dot gnu.org
2023-10-24 10:04 ` vincenzo.innocente at cern dot ch
2023-10-24 12:27 ` redi at gcc dot gnu.org
2023-10-24 12:38 ` vincenzo.innocente at cern dot ch
2023-10-24 15:55 ` redi at gcc dot gnu.org
2023-10-24 16:27 ` vincenzo.innocente at cern dot ch
2023-10-24 16:28 ` redi at gcc dot gnu.org
2023-10-25 10:28 ` cvs-commit at gcc dot gnu.org [this message]
2023-10-25 14:21 ` cvs-commit at gcc dot gnu.org
2023-10-25 14:35 ` cvs-commit at gcc dot gnu.org
2023-10-25 14:36 ` redi 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-111936-4-9WY7urRCJU@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: 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).