Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: John Baldwin <jhb@freebsd.org>, gdb@sourceware.org
Subject: Re: C++ conversion status update
Date: Wed, 20 Jan 2016 11:10:00 -0000	[thread overview]
Message-ID: <569F6B1D.60406@redhat.com> (raw)
In-Reply-To: <290689073.6kaHW0HruR@ralph.baldwin.cx>

On 01/19/2016 07:00 PM, John Baldwin wrote:
> On Monday, December 14, 2015 07:09:08 PM Pedro Alves wrote:
>> On 12/14/2015 02:40 PM, Yao Qi wrote:
>> Meanwhile, I tried a few BSD hosts on the compile farm and
>> wrote a few patches:
>>
>>   https://github.com/palves/gdb/commits/palves/cxx-conversion-netbsd
>>
>> but haven't had a moment yet to drive them to completion.  I probably should sync
>> up with Simon though, as I think I may be duplicating work he's done already.
> 
> I started doing some test builds on FreeBSD with C++ today and ran into one
> unexpected thing that I'm not sure how to fix.

Thanks!

> 
> I build gdb from git on my own for testing, but the gdb package for FreeBSD
> users is built from FreeBSD's ports framework.  The framework sets default
> CFLAGS / CXXFLAGS values for the ports it builds (and each port can
> override or adjust those as needed).  However, gdb uses CFLAGS instead of
> CXXFLAGS when building with C++.  The default flags in FreeBSD's ports
> infrastructure include "-std=gnu89" in the default CFLAGS (but not in
> CXXFLAGS since it is a C-only flag).  The CXXFLAGS set in the environment
> when ./configure was run do not appear to be honored in the generated
> gdb/Makefile and also don't appear to be used during the build of gdb
> itself.

Indeed, thanks for noticing this.  I've sent a patch now:
  https://sourceware.org/ml/gdb-patches/2016-01/msg00469.html

I've also pushed it to:
  git@github.com:palves/gdb.git palves/cxx-conversion-attempt-part-2-no-fpermissive

(note there are a few more wip/pending C++ patches on that branch)

Could you give it a try?

Thanks,
Pedro Alves


  reply	other threads:[~2016-01-20 11:10 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24 13:07 Pedro Alves
2015-12-14 14:40 ` Yao Qi
2015-12-14 19:09   ` Pedro Alves
2015-12-15 11:39     ` Jose E. Marchesi
2015-12-15 20:03       ` Simon Marchi
2015-12-16  0:19         ` Pedro Alves
2015-12-16  0:21           ` Pedro Alves
2015-12-16  1:19             ` Simon Marchi
2015-12-16 20:11               ` Pedro Alves
2015-12-16 20:15       ` Pedro Alves
2015-12-16 20:30         ` Simon Marchi
2015-12-16 22:10           ` Pedro Alves
2015-12-16 22:59             ` Pedro Alves
2016-01-19 19:00     ` John Baldwin
2016-01-20 11:10       ` Pedro Alves [this message]
2016-01-20 23:33         ` John Baldwin
2016-01-21 11:38           ` Pedro Alves
2016-04-16  0:21           ` Pedro Alves
2016-04-18 16:51             ` Pedro Alves
2016-04-19 19:26               ` John Baldwin
2016-04-19 20:36                 ` Pedro Alves
2016-04-19 21:40                   ` John Baldwin
2016-04-19 22:20                     ` Pedro Alves
2016-04-13  0:25     ` Pedro Alves
2016-04-13 11:07       ` Yao Qi
2016-04-13 14:13         ` Pedro Alves
2016-04-13 14:31           ` Sergio Durigan Junior
2016-04-13 12:41       ` Joel Brobecker
2016-04-13 14:04         ` Pedro Alves
2016-04-13 14:16           ` Joel Brobecker
2016-04-13 14:27             ` Luis Machado
2016-04-13 14:35             ` Marc Khouzam
2016-04-13 14:59               ` Joel Brobecker
2016-04-13 14:40             ` Pedro Alves
2016-04-18 17:29               ` 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=569F6B1D.60406@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=jhb@freebsd.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