From: Jonathan Wakely <jwakely@redhat.com>
To: "Björn Schäpers" <gcc@hazardy.de>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org,
"Björn Schäpers" <bjoern@hazardy.de>
Subject: Re: [PATCH] libstdc++: enable <stacktrace> on windows
Date: Sat, 14 Jan 2023 22:02:06 +0000 [thread overview]
Message-ID: <CACb0b4mM8DeyJpsC2euyPeN7nvVoaqrm3yP-na_5gZZ6uGqtNQ@mail.gmail.com> (raw)
In-Reply-To: <20221212172749.49723-1-gcc@hazardy.de>
On Mon, 12 Dec 2022 at 17:28, Björn Schäpers <gcc@hazardy.de> wrote:
>
> From: Björn Schäpers <bjoern@hazardy.de>
>
> libstdc++-v3/Changelog
> * acinclude.m4: Add check for windows.h.
> * acinclude.m4: Add pecoff as FORMAT_FILE.
> * config.h.in: Regenerate.
> * configure: Regenerate.
> * src/libbacktrace/Makefile.am: Regenerate.
> * src/libbacktrace/Makefile.in: Add pecoff.c as FORMAT_FILE.
Thanks, I've pushed this one too.
>
> Signed-off-by: Björn Schäpers <bjoern@hazardy.de>
> ---
> libstdc++-v3/acinclude.m4 | 2 ++
> libstdc++-v3/src/libbacktrace/Makefile.am | 1 +
> 2 files changed, 3 insertions(+)
>
> diff --git a/libstdc++-v3/acinclude.m4 b/libstdc++-v3/acinclude.m4
> index b957c728ba1..1cfe704e637 100644
> --- a/libstdc++-v3/acinclude.m4
> +++ b/libstdc++-v3/acinclude.m4
> @@ -4981,6 +4981,7 @@ AC_DEFUN([GLIBCXX_ENABLE_BACKTRACE], [
> if test "$have_dl_iterate_phdr" = "yes"; then
> BACKTRACE_CPPFLAGS="$BACKTRACE_CPPFLAGS -DHAVE_DL_ITERATE_PHDR=1"
> fi
> + AC_CHECK_HEADERS(windows.h)
>
> # Check for the fcntl function.
> if test -n "${with_target_subdir}"; then
> @@ -5026,6 +5027,7 @@ glibcxx_cv_sys_filetype=$filetype])
> FORMAT_FILE=
> case "$glibcxx_cv_sys_filetype" in
> elf*) FORMAT_FILE="elf.lo" ;;
> +pecoff*) FORMAT_FILE="pecoff.lo" ;;
> *) AC_MSG_WARN([could not determine output file type])
> FORMAT_FILE="unknown.lo"
> enable_libstdcxx_backtrace=no
> diff --git a/libstdc++-v3/src/libbacktrace/Makefile.am b/libstdc++-v3/src/libbacktrace/Makefile.am
> index 52d8f81b97b..b34a429a21d 100644
> --- a/libstdc++-v3/src/libbacktrace/Makefile.am
> +++ b/libstdc++-v3/src/libbacktrace/Makefile.am
> @@ -71,6 +71,7 @@ libstdc___libbacktrace_la_SOURCES = \
>
> FORMAT_FILES = \
> elf.c \
> + pecoff.c \
> unknown.c
>
> VIEW_FILES = \
> --
> 2.38.1
>
prev parent reply other threads:[~2023-01-14 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 17:27 Björn Schäpers
2023-01-14 22:02 ` Jonathan Wakely [this message]
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=CACb0b4mM8DeyJpsC2euyPeN7nvVoaqrm3yP-na_5gZZ6uGqtNQ@mail.gmail.com \
--to=jwakely@redhat.com \
--cc=bjoern@hazardy.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@hazardy.de \
--cc=libstdc++@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).