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: Wed, 06 Oct 2021 13:03:54 +0000	[thread overview]
Message-ID: <bug-28413-4717-Yq3HICTzVK@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 #8 from Simon Marchi <simark at simark dot ca> ---
(In reply to Bruno Haible from comment #7)
> (In reply to Simon Marchi from comment #6)
> > This one is on an Arch Linux system, updated a few
> > weeks ago.  It has:
> > 
> >  - gcc 11.1.0-1
> >  - glibc 2.33-5
> 
> Still more information needed:
>   - Do you have Gnulib's c++defs.h, or the one by Enze Li?
>   - Do the compiler options that are being passed for this compilation unit
> include optimization options (-O*)?

 - It's the c++defs.h in GDB's source tree, so the one from gnulib commit
776af40e09b476a41073131a90022572f448c189, unmodified.
 - No optimization.  The full compilation command line is:

   clang++ -x c++    -I. -I/home/simark/src/binutils-gdb/gdb
-I/home/simark/src/binutils-gdb/gdb/config
-DLOCALEDIR="\"/usr/local/share/locale\"" -DHAVE_CONFIG_H
-I/home/simark/src/binutils-gdb/gdb/../include/opcode
-I/home/simark/src/binutils-gdb/gdb/../readline/readline/..
-I/home/simark/src/binutils-gdb/gdb/../zlib -I../bfd
-I/home/simark/src/binutils-gdb/gdb/../bfd
-I/home/simark/src/binutils-gdb/gdb/../include -I../libdecnumber
-I/home/simark/src/binutils-gdb/gdb/../libdecnumber 
-I/home/simark/src/binutils-gdb/gdb/../gnulib/import -I../gnulib/import
-I/home/simark/src/binutils-gdb/gdb/.. -I..
-I/home/simark/src/binutils-gdb/gdb/../libbacktrace/ -I../libbacktrace/ 
-DTUI=1    -I/usr/include/guile/2.0 -pthread  -I/usr/include/python3.9
-I/usr/include/python3.9   -I/home/simark/src/binutils-gdb/gdb/.. -pthread 
-Wall -Wpointer-arith -Wno-unused -Wunused-value -Wunused-function -Wno-switch
-Wno-char-subscripts -Wempty-body -Wno-sign-compare -Wno-mismatched-tags
-Wno-error=deprecated-register -Wsuggest-override -Wdeprecated-copy
-Wdeprecated-copy-dtor -Wredundant-move -Wmissing-declarations
-Wmissing-prototypes -Wformat -Wformat-nonliteral -Werror -g3 -O0
-D_GLIBCXX_DEBUG=1 -ferror-limit=1   -c -o unittests/string_view-selftests.o
-MT unittests/string_view-selftests.o -MMD -MP -MF
unittests/.deps/string_view-selftests.Tpo
/home/simark/src/binutils-gdb/gdb/unittests/string_view-selftests.c

I gave the gcc version, but the problem is actually when compiling with clang,
so here's the clang version:

$ clang++ --version
clang version 12.0.1

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

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