public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/28413] string_view-selftests.c build error on macOS
Date: Mon, 04 Oct 2021 15:13:07 +0000	[thread overview]
Message-ID: <bug-28413-4717-l8DWlsGAKN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28413-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28413

--- Comment #4 from Simon Marchi <simark at simark dot ca> ---
Well, now I get this, but I have definitely seen the fdopen one in the past:

  CXX    unittests/string_view-selftests.o
In file included from
/home/simark/src/binutils-gdb/gdb/unittests/string_view-selftests.c:26:
In file included from /home/simark/src/binutils-gdb/gdb/defs.h:28:
In file included from
/home/simark/src/binutils-gdb/gdb/../gdbsupport/common-defs.h:95:
../gnulib/import/string.h:693:1: error: reference to overloaded function could
not be resolved; did you mean to call it?
_GL_CXXALIASWARN (memchr);
^~~~~~~~~~~~~~~~~~~~~~~~~
../gnulib/import/sys/select.h:430:4: note: expanded from macro
'_GL_CXXALIASWARN'
   _GL_CXXALIASWARN_1 (func, GNULIB_NAMESPACE)
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../gnulib/import/sys/select.h:432:4: note: expanded from macro
'_GL_CXXALIASWARN_1'
   _GL_CXXALIASWARN_2 (func, namespace)
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../gnulib/import/sys/select.h:437:5: note: expanded from macro
'_GL_CXXALIASWARN_2'
    _GL_WARN_ON_USE (func, \
    ^~~~~~~~~~~~~~~~~~~~~~~~
../gnulib/import/sys/select.h:572:19: note: expanded from macro
'_GL_WARN_ON_USE'
extern __typeof__ (function) function \
                  ^~~~~~~~~~
/usr/include/string.h:73:20: note: possible target for call
extern const void *memchr (const void *__s, int __c, size_t __n)
                   ^
/usr/include/string.h:71:14: note: possible target for call
extern void *memchr (void *__s, int __c, size_t __n)
             ^

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-10-04 15:13 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 [this message]
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
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-l8DWlsGAKN@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).