Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: John Baldwin <jhb@freebsd.org>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <palves@redhat.com>,
	Walfred Tedeschi <walfred.tedeschi@intel.com>,
	"Simon Marchi; gdb-patches"@sourceware.org
Subject: Re: [PATCH 0/1] Build GDB as a C++ program by default
Date: Thu, 21 Apr 2016 15:18:00 -0000	[thread overview]
Message-ID: <4644337.bLejKkzcMH@ralph.baldwin.cx> (raw)
In-Reply-To: <5717DED3.9020107@redhat.com>

On Wednesday, April 20, 2016 08:56:03 PM Pedro Alves wrote:
> On 04/19/2016 04:20 PM, Walfred Tedeschi wrote:
> > Am 4/19/2016 um 4:39 PM schrieb Pedro Alves:
> >> On 04/19/2016 03:36 PM, Walfred Tedeschi wrote:
> >>
> >>> Pedro,
> >>>
> >>> Do you have some data about building GDB on OsX with
> >>> --enable-build-with-cxx?
> >>>
> >>> If not I could give it a try!
> >>
> >> Please do give it a try.  Thanks!
> >>
> > 
> > There is some issues, i will investigating a bit further.
> > By now i was compiling with Clang, will also try to compile with gcc.
> 
> I managed to build a linux x darwin cross compiler here, using the
> osxcross tool.
> 
> Indeed, clang++ stumbles on a bunch of issues.  But then again, so
> does clang in C-mode.

If you are interested in fixing clang warnings I can submit some patches as
I tend to build gdb with clang on FreeBSD.  It gets really unhappy about
unused functions from the VEC() generators which adds quite a bit of noise,
but some of the things it finds are actual bugs (though probably harmless
ones).

-- 
John Baldwin


  parent reply	other threads:[~2016-04-21 15:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18 17:27 Pedro Alves
2016-04-18 17:27 ` [PATCH 1/1] " Pedro Alves
2016-04-19  7:34   ` Yao Qi
2016-04-19 13:34 ` [PATCH 0/1] " Simon Marchi
2016-04-19 14:18   ` Pedro Alves
2016-04-19 14:48     ` Eli Zaretskii
2016-04-19 15:03       ` Pedro Alves
2016-04-19 15:23         ` Eli Zaretskii
2016-04-19 15:40           ` Pedro Alves
2016-04-19 15:59             ` Eli Zaretskii
2016-04-19 16:20               ` Pedro Alves
2016-04-19 16:31               ` Eli Zaretskii
2016-04-19 15:41       ` Simon Marchi
2016-04-19 16:32         ` Eli Zaretskii
     [not found]     ` <AC542571535E904D8E8ADAE745D60B19445B1C11@IRSMSX104.ger.corp.intel.com>
     [not found]       ` <5716425B.3050707@intel.com>
     [not found]         ` <57164325.8020408@redhat.com>
2016-04-19 15:20           ` Walfred Tedeschi
2016-04-20 19:56             ` Pedro Alves
2016-04-20 22:16               ` Pedro Alves
2016-04-21 15:18               ` John Baldwin [this message]
2016-04-21 16:41                 ` Pedro Alves
2016-04-19 15:47     ` Simon Marchi
2016-04-19 15:50       ` Pedro Alves
2016-04-20 22:27     ` Pedro Alves

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=4644337.bLejKkzcMH@ralph.baldwin.cx \
    --to=jhb@freebsd.org \
    --cc="Simon Marchi; gdb-patches"@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=walfred.tedeschi@intel.com \
    /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