From: Thiago Jung Bauermann via Gdb <gdb@sourceware.org>
To: Li Hua via Gdb <gdb@sourceware.org>
Cc: "bug-gdb@gnu.org" <bug-gdb@gnu.org>, Li Hua <boredcola@outlook.com>
Subject: Re: bugs happen when building in darwin
Date: Fri, 31 Jan 2025 22:53:47 -0300 [thread overview]
Message-ID: <87a5b6ctw4.fsf@linaro.org> (raw)
In-Reply-To: <SI2PR02MB461726880CACB3861F7A0E0AA3E82@SI2PR02MB4617.apcprd02.prod.outlook.com> (Li Hua via Gdb's message of "Sat, 1 Feb 2025 00:29:50 +0000")
Hello,
Li Hua via Gdb <gdb@sourceware.org> writes:
> 3:Error(happen when do the 'make' processs):
> darwin-nat.c:1949:21: error: use of undeclared identifier 'command_style'
> styled_string (command_style.style (), "run"),
> ^
> darwin-nat.c:1950:21: error: use of undeclared identifier 'command_style'
> styled_string (command_style.style (),
> ^
> darwin-nat.c:1959:20: error: use of undeclared identifier 'command_style'
> styled_string (command_style.style (), "run"),
>
>
> To this problem, I have personally tried to fix it. And I found the reason causing this error is that the header file "cli/cli-style.h" doesn't been included in "darwin-nat.c". When I add the line '#include "cli/cli-style.h"'
> , the error disappears.
>
> Thank you for reading this. Looking forward your reply.
Thank you for your detailed report! This has also been reported a few
days ago here:
https://sourceware.org/bugzilla/show_bug.cgi?id=32610
The fix you mention has been committed. A new GDB 16.2 release will be
done shortly that will include it.
As an aside, the bug-gdb mailing list has been discontinued. In the
future, it's best to either file a new bug report
https://sourceware.org/bugzilla/ or send an email to the
gdb@sourceware.org mailing list.
--
Thiago
prev parent reply other threads:[~2025-02-01 1:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-01 0:29 Li Hua via Gdb
2025-02-01 1:53 ` Thiago Jung Bauermann via Gdb [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=87a5b6ctw4.fsf@linaro.org \
--to=gdb@sourceware.org \
--cc=boredcola@outlook.com \
--cc=bug-gdb@gnu.org \
--cc=thiago.bauermann@linaro.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