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:01:00 -0000	[thread overview]
Message-ID: <6899ECC3-F9E6-4203-8B09-D9F4B279263E@comcast.net> (raw)
In-Reply-To: <D029885B-D093-4416-9957-371E3D08495E@comcast.net>



> On Apr 27, 2018, at 2:44 PM, Paul Koning <paulkoning@comcast.net> wrote:
> 
> 
> 
>> On Apr 27, 2018, at 2:02 PM, Simon Marchi <simon.marchi@polymtl.ca> wrote:
>> 
>> On 2018-04-26 19:48, Paul Koning wrote:
>>> I can't build GDB on Mac.  This shows up both in a native build, and a
>>> cross-build (for example target=mips-netbsdelf).  I see this error:
>>> /Users/pkoning/Downloads/gdb-8.1/gdb/stap-probe.c:122:29: error: default
>>>     initialization of an object of const type 'const stap_static_probe_ops'
>>>     without a user-provided default constructor
>>> const stap_static_probe_ops stap_static_probe_ops;
>>> or
>>> /Users/pkoning/Downloads/gdb-8.1/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;
>>> (same problem, different source file).
>>> 	paul
>> 
>> Hi Paul,
>> 
>> What is the compiler, which version, and can you share the full command line used to compile probe.o, for example?
>> 
>> Simon
> ...
> These appear to be LLVM incompatibilities; if I feed those command lines to (real) GCC 8.0, just built yesterday from current trunk, they compile cleanly.

To follow up on that: if I force the use of real GCC/G++ (with CC and CXX definitions in the configure command), I get a successful build for the native case.  I'm trying a cross-build now.

	paul


  reply	other threads:[~2018-04-27 18:57 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 [this message]
2018-04-27 19:08     ` Simon Marchi
2018-04-27 19:18       ` Paul Koning
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=6899ECC3-F9E6-4203-8B09-D9F4B279263E@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