public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "levraiphilippeblain at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/28413] string_view-selftests.c build error on macOS
Date: Fri, 11 Feb 2022 13:11:58 +0000 [thread overview]
Message-ID: <bug-28413-4717-w1oAIi1QwP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28413-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28413
Philippe Blain <levraiphilippeblain at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |levraiphilippeblain at gmail dot c
| |om
--- Comment #9 from Philippe Blain <levraiphilippeblain at gmail dot com> ---
I can confirm the original build error reported by Enze Li (fdopen on macOS)
still occurs for current master with both (macOS 10.11 + clang 13) and (macOS
10.15 + clang 12) [1].
The patch sent to gnulib (link in [2] above) was not well received, and Bruno
indicated that gnulib does not support '-Werror' [3], which is automatically
applied for GDB builds from Git if I'm not mistaken.
I'm not sure of what could be done to fix the issue...
It seems weird that gnulib issues a warning for a system include (here libc++),
as this would be outside the control of projects using gnulib, so maybe it
could be disabled somehow for system includes ?
[1]
https://github.com/phil-blain/binutils-gdb/runs/5145831559?check_suite_focus=true#step:5:4227
[2] https://sourceware.org/bugzilla/show_bug.cgi?id=28413#c2
[3] https://lists.gnu.org/archive/html/bug-gnulib/2021-10/msg00005.html
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-02-11 13:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 8:54 [Bug build/28413] New: " lienze2010 at hotmail dot com
2021-10-04 12:18 ` [Bug build/28413] " simark at simark dot ca
2021-10-04 14:33 ` vries at gcc dot gnu.org
2021-10-04 14:46 ` vries at gcc dot gnu.org
2021-10-04 15:13 ` simark at simark dot ca
2021-10-06 0:11 ` bruno at clisp dot org
2021-10-06 0:19 ` simark at simark dot ca
2021-10-06 12:32 ` bruno at clisp dot org
2021-10-06 13:03 ` simark at simark dot ca
2022-02-11 13:11 ` levraiphilippeblain at gmail dot com [this message]
2022-10-18 13:48 ` lienze at sourceware dot org
2022-11-15 4:00 ` research_trasio at irq dot a4lg.com
2022-11-15 13:43 ` lienze at sourceware dot org
2022-11-15 13:44 ` lienze at sourceware dot org
2022-11-15 13:47 ` vries at gcc dot gnu.org
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-28413-4717-w1oAIi1QwP@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).