public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "wilson at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/26949] ELF target support seems broken on macOS 11
Date: Fri, 27 Nov 2020 23:29:02 +0000 [thread overview]
Message-ID: <bug-26949-4717-plNYss9O9F@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26949-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26949
Jim Wilson <wilson at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wilson at gcc dot gnu.org
--- Comment #1 from Jim Wilson <wilson at gcc dot gnu.org> ---
The linux compilers (gcc and clang) give a warning by default when a system
header file is missing. The MacOS compiler is giving an error by default. It
appears to be a configuration choice on the MacOS side. So some stuff that
builds with a warning on linux will fail to build on macos. I ran into this
same problem with riscv-gnu-toolchain recently.
This looks like more failout from the CTF changes that added a call to strncmp
to elf-bfd.h, so anything that includes elf-bfd.h now needs to also include
string.h or it won't work on macos, and there is one place in configure.ac that
is using elf-bfd.h but not including string.h.
The proposed change looks reasonable to me. I'm not a gdb maintainer though.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-11-27 23:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 10:00 [Bug gdb/26949] New: " eblot.ml at gmail dot com
2020-11-26 13:15 ` [Bug gdb/26949] " eblot.ml at gmail dot com
2020-11-27 23:29 ` wilson at gcc dot gnu.org [this message]
2021-01-05 11:17 ` big_deady2 at web dot de
2021-01-05 16:00 ` simark at simark dot ca
2021-01-06 11:10 ` eblot.ml at gmail dot com
2021-02-09 1:54 ` sify21 at 163 dot com
2021-02-18 13:59 ` keller at metrolab dot com
2021-02-18 15:35 ` simark at simark dot ca
2021-02-22 12:46 ` keller at metrolab dot com
2021-02-22 16:40 ` simark at simark dot ca
2021-02-22 18:20 ` eblot.ml at gmail dot com
2021-02-22 18:47 ` keller at metrolab dot com
2021-02-22 18:48 ` keller at metrolab dot com
2021-02-22 20:03 ` simark at simark dot ca
2021-02-22 22:21 ` keller at metrolab dot com
2021-02-23 1:42 ` simark at simark dot ca
2021-02-23 7:17 ` keller at metrolab dot com
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=bug-26949-4717-plNYss9O9F@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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).