Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paul Koning <paulkoning@comcast.net>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: GDB 8.1 build error
Date: Fri, 27 Apr 2018 19:18:00 -0000	[thread overview]
Message-ID: <245849C1-8B07-4305-9DFC-8CCE1FE90A73@comcast.net> (raw)
In-Reply-To: <77e31c8f87342c5753d1d622fa7574ff@polymtl.ca>



> On Apr 27, 2018, at 3:01 PM, Simon Marchi <simon.marchi@polymtl.ca> wrote:
> 
> ...
> This seems to be a bogus error that was fixed in clang 3.9:
> 
> https://stackoverflow.com/questions/7411515/why-does-c-require-a-user-provided-default-constructor-to-default-construct-a?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa
> 
> You Apple LLVM 7.3.0 seems to map to upstream clang 3.8.0:
> 
> https://en.wikipedia.org/wiki/Xcode#Latest_versions
> 
> I indeed get the same error if I try building the file with clang 3.8 on Linux:
> 
> $ clang++-3.8 -x c++ -std=gnu++11 -g3 -O0 <snip> /home/emaisin/src/binutils-gdb/gdb/probe.c
> /home/emaisin/src/binutils-gdb/gdb/probe.c:63:28: error: default initialization of an object of
>      const type 'const any_static_probe_ops' without a user-provided default constructor
> const any_static_probe_ops any_static_probe_ops;
>                           ^
> 
> If compatibility with clang 3.8 is really important to you, we could always add an empty constructor to that class.  Otherwise, if it's easy for you to update your Xcode, I'd say try that first.

I foolishly assumed that the Apple updater would update Apple stuff.  And indeed it has given me bugfix updates to Xcode Command Line in the past.  But it doesn't do Xcode version updates.  

You're right, I'm way out of date, and that was unintentional.  I'm getting the latest now.  Will try with that and report.

	paul



  reply	other threads:[~2018-04-27 19:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-27 18:02 Paul Koning
2018-04-27 18:38 ` Simon Marchi
2018-04-27 18:57   ` Paul Koning
2018-04-27 19:01     ` Paul Koning
2018-04-27 19:08     ` Simon Marchi
2018-04-27 19:18       ` Paul Koning [this message]
2018-04-27 20:41       ` Paul Koning
2018-04-27 19:10     ` Pedro Alves
2018-04-27 19:39       ` Simon Marchi
2018-04-27 20:00         ` Pedro Alves
2018-04-27 20:16         ` Pedro Alves
2018-04-27 20:24           ` Simon Marchi
2018-04-27 20:41             ` Pedro Alves
2018-04-27 20:48               ` Simon Marchi
2018-05-02  9:42                 ` Pedro Alves
2018-05-02 10:13                   ` Pedro Alves
2018-04-27 19:10     ` Simon Marchi

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=245849C1-8B07-4305-9DFC-8CCE1FE90A73@comcast.net \
    --to=paulkoning@comcast.net \
    --cc=gdb@sourceware.org \
    --cc=simon.marchi@polymtl.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