From: Eli Zaretskii via Gdb <gdb@sourceware.org>
To: Simon Marchi <simark@simark.ca>
Cc: chrisj@rtems.org, gdb@sourceware.org
Subject: Re: GDB 13.1 and clang
Date: Thu, 09 Mar 2023 09:07:18 +0200 [thread overview]
Message-ID: <83sfee2yjd.fsf@gnu.org> (raw)
In-Reply-To: <6a40e8de-f2c0-32a3-2bed-3a4c430f71d7@simark.ca> (message from Simon Marchi via Gdb on Wed, 8 Mar 2023 16:36:45 -0500)
> Date: Wed, 8 Mar 2023 16:36:45 -0500
> From: Simon Marchi via Gdb <gdb@sourceware.org>
>
> > There is another version installed here:
> >
> > $ pkg which /usr/local/include/diagnostics.h
> > /usr/local/include/diagnostics.h was installed by package binutils-2.37_2,1
> >
> > We have /usr/local/include early in the include list on FreeBSD to pick up some
> > of the required libraries installed as packages. I will check for a package
> > update or I revisit the build flags to see how it can be handled.
> Huh, diagnostics.h is an internal header file, I don't think binutils
> packages should ship it. I just looked up, and Ubuntu and Arch packages
> ship it as well... sigh.
diagnostics.h is included by bfd.h, which is installed by Binutils'
"make install", so I don't think they can avoid shipping
diagnostics.h. They should maybe have a separate header file for
that, under some FOO_internal.h name or something, which could serve
for that purpose. But this should be taken up with Binutils
maintainers, of course.
next prev parent reply other threads:[~2023-03-09 7:07 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 via Gdb
2023-03-08 20:22 ` Simon Marchi via Gdb
2023-03-08 21:22 ` Chris Johns
2023-03-08 21:36 ` Simon Marchi via Gdb
2023-03-08 21:41 ` Chris Johns
2023-03-08 22:07 ` Joel Sherrill
2023-03-09 7:07 ` Eli Zaretskii via Gdb [this message]
2023-03-08 22:53 ` John Baldwin
2023-03-09 2:15 ` Simon Marchi via Gdb
2023-03-09 3:20 ` Chris Johns
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=83sfee2yjd.fsf@gnu.org \
--to=gdb@sourceware.org \
--cc=chrisj@rtems.org \
--cc=eliz@gnu.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