From: Joel Sherrill <joel@rtems.org>
To: Chris Johns <chrisj@rtems.org>
Cc: Simon Marchi <simark@simark.ca>,
Eli Zaretskii via Gdb <gdb@sourceware.org>
Subject: Re: GDB 13.1 and clang
Date: Wed, 8 Mar 2023 15:07:42 -0700 [thread overview]
Message-ID: <CAF9ehCVcgygdVP6QOK16RWT-G-PH2dDB8i-EaJb8Axt2y7ChbA@mail.gmail.com> (raw)
In-Reply-To: <84f213b6-dd2a-9618-9f92-6cef3276a72a@rtems.org>
On Wed, Mar 8, 2023, 2:41 PM Chris Johns <chrisj@rtems.org> wrote:
> On 9/3/2023 6:36 am, Simon Marchi wrote:
> >> 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.
>
> Ah, that is awkward as removing it from shipped packages is something we
> cannot
> reach back and fix.
>
And it could be in other packaging systems. Mays, Cyg
>
Admittedly not checking but is this header installed as part of make
install? I wouldn't think anyone would package something not installed.
>
> Rename diagnostics.h?
>
Works but rather awful.
Is it worth a check it's installed and there's a conflict?
--joel
>
> Chris
>
next prev parent reply other threads:[~2023-03-08 22:08 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 [this message]
2023-03-09 7:07 ` Eli Zaretskii via Gdb
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=CAF9ehCVcgygdVP6QOK16RWT-G-PH2dDB8i-EaJb8Axt2y7ChbA@mail.gmail.com \
--to=joel@rtems.org \
--cc=chrisj@rtems.org \
--cc=gdb@sourceware.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