Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gdb-patches@sourceware.org
Subject: Re: Fix gdb 7.12 C++ compilation on Solaris
Date: Wed, 19 Oct 2016 12:20:00 -0000	[thread overview]
Message-ID: <54379347-b202-16c0-2d22-d50e101d4394@redhat.com> (raw)
In-Reply-To: <ydd7f94y2qj.fsf@CeBiTec.Uni-Bielefeld.DE>

On 10/19/2016 12:53 PM, Rainer Orth wrote:

> Besides, given that GCC 4.9 was the last version to support Solaris 9,
> one might consider deprecating/removing anything before Solaris 10 in
> gdb, too.

That's be fine with me, but then again, I don't really use
Solaris at all.  :-)

> 
> I'll see if I can find some spare cycles to clean procfs.c and friends
> up: there are tons of opportunities with anything but Solaris gone as
> clients of that file and a couple related ones.
> 
>> FYI, AFAIK, no GDB maintainer cares for/tests on Solaris
>> routinely nowadays.
> 
> Neither do I: just whenever a new gdb or binutils release arrives, I
> give them a try.  I'm way behind even on Solaris/gcc maintenance, so I
> fear there's not much I can do about gdb on that front.  However,
> there's a couple of Solaris patches for gdb 7.11 here:
> 
> 	https://java.net/projects/solaris-userland/sources/gate/show/components/gdb/patches?rev=7127
> 
> Perhaps the authors can be motivated to contribute them upstream as they
> obviously intended ;-)

Indeed.  (That page is not opening for me, server seems slow, can't see
what the patches are about.)


> 
>>> Still ok for mainline?
>>
>> Still OK.
> 
> Thanks.  I'll commit as soon as I've sorted some problem with hg-git
> out: plain git is completely unusable for me.
> 

Thanks.

(FYI, we don't just put the ChangeLog entry in the commit log
like gcc does.  If you include the description of the problem as you
had in the email in the git commit log, that'd be great.)

> What about the 7.12 branch backport with the PR now filed?

You just need to cherry pick the fix to the gdb-7.12-branch branch
and push it.  Just leave the atof call in place under !__cplusplus
in the branch version, like you had in the original version, in case
that was really necessary on some host.

Thanks,
Pedro Alves


  reply	other threads:[~2016-10-19 12:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14 14:47 Rainer Orth
2016-10-14 15:08 ` Pedro Alves
2016-10-18 13:14   ` Rainer Orth
2016-10-18 14:28     ` Pedro Alves
2016-10-19 11:53       ` Rainer Orth
2016-10-19 12:20         ` Pedro Alves [this message]
2016-10-25 14:19           ` Rainer Orth

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=54379347-b202-16c0-2d22-d50e101d4394@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    /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