From: Chris Johns <chrisj@rtems.org>
To: Simon Marchi <simark@simark.ca>, John Baldwin <jhb@FreeBSD.org>,
gdb@sourceware.org
Subject: Re: GDB 13.1 and clang
Date: Thu, 9 Mar 2023 14:20:22 +1100 [thread overview]
Message-ID: <e4f91d7c-5890-082f-5f97-40d82e4f90ce@rtems.org> (raw)
In-Reply-To: <fcc7e0a6-8911-4f24-b63d-477a8e404b70@simark.ca>
On 9/3/2023 11:15 am, Simon Marchi wrote:
>> On 3/8/23 17:53, John Baldwin wrote:
>> diff --git a/gdb/Makefile.in b/gdb/Makefile.in
>> index 6e39383eb93..40497541880 100644
>> --- a/gdb/Makefile.in
>> +++ b/gdb/Makefile.in
>> @@ -629,8 +629,8 @@ INTERNAL_CPPFLAGS = $(CPPFLAGS) @GUILE_CPPFLAGS@ @PYTHON_CPPFLAGS@ \
>> # INTERNAL_CFLAGS is the aggregate of all other *CFLAGS macros.
>> INTERNAL_CFLAGS_BASE = \
>> $(GLOBAL_CFLAGS) $(PROFILE_CFLAGS) \
>> - $(GDB_CFLAGS) $(OPCODES_CFLAGS) $(READLINE_CFLAGS) $(ZLIBINC) \
>> - $(ZSTD_CFLAGS) $(BFD_CFLAGS) $(INCLUDE_CFLAGS) $(LIBDECNUMBER_CFLAGS) \
>> + $(GDB_CFLAGS) $(OPCODES_CFLAGS) $(BFD_CFLAGS) $(INCLUDE_CFLAGS) \
>> + $(READLINE_CFLAGS) $(ZLIBINC) $(ZSTD_CFLAGS) $(LIBDECNUMBER_CFLAGS) \
>> $(INTL_CFLAGS) $(INCGNU) $(INCSUPPORT) $(LIBBACKTRACE_INC) \
>> $(ENABLE_CFLAGS) $(INTERNAL_CPPFLAGS) $(SRCHIGH_CFLAGS) \
>> $(TOP_CFLAGS) $(PTHREAD_CFLAGS) $(DEBUGINFOD_CFLAGS) $(GMPINC) \
>
> If it works, I'd be fine with that patch. We'll need a PR number for
> the patch to make it to the 13 branch though.
I have raised a ticket ..
https://sourceware.org/bugzilla/show_bug.cgi?id=30214
Chris
next prev parent reply other threads:[~2023-03-09 3:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 20:07 Chris Johns
2023-03-08 20:16 ` Andrew Pinski
2023-03-08 20:22 ` Simon Marchi
2023-03-08 21:22 ` Chris Johns
2023-03-08 21:36 ` Simon Marchi
2023-03-08 21:41 ` Chris Johns
2023-03-08 22:07 ` Joel Sherrill
2023-03-09 7:07 ` Eli Zaretskii
2023-03-08 22:53 ` John Baldwin
2023-03-09 2:15 ` Simon Marchi
2023-03-09 3:20 ` Chris Johns [this message]
2023-03-09 2:41 ` Chris Johns
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=e4f91d7c-5890-082f-5f97-40d82e4f90ce@rtems.org \
--to=chrisj@rtems.org \
--cc=gdb@sourceware.org \
--cc=jhb@FreeBSD.org \
--cc=simark@simark.ca \
/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).