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>, gdb-patches@sourceware.org
Subject: Re: Fix gdb 8.1 Solaris compilation
Date: Thu, 21 Sep 2017 14:21:00 -0000	[thread overview]
Message-ID: <494a8b5e-a059-457c-61ad-f4edb2573a2c@redhat.com> (raw)
In-Reply-To: <yddy3p8p5l6.fsf@CeBiTec.Uni-Bielefeld.DE>

On 09/21/2017 02:02 PM, Rainer Orth wrote:

> With the changes below, I can build gdb on sparcv9-sun-solaris2.11 and
> amd64-pc-solaris2.11 and a simple smoke test (gdb/gdb gdb/gdb) works.
> 
> Ok for mainline?
> 

OK.

(Since you posted a non-'git format-patch' patch, I feel compelled
to say: please remember to push with meaningful git subject line
and commit log.)

Thanks,
Pedro Alves


  parent reply	other threads:[~2017-09-21 14:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21 13:02 Rainer Orth
2017-09-21 13:17 ` Andreas Schwab
2017-09-21 14:14   ` Rainer Orth
2017-09-21 14:31     ` Obsolete/remove Solaris < 10 [was: Re: Fix gdb 8.1 Solaris compilation] Rainer Orth
2017-09-21 14:39       ` Pedro Alves
2017-09-22 14:45         ` Rainer Orth
2017-09-22 15:40           ` Pedro Alves
2017-09-26 11:20             ` Rainer Orth
2017-09-26 11:26               ` Pedro Alves
2017-09-26 13:25                 ` Rainer Orth
2017-09-26 13:45                   ` Pedro Alves
2017-09-26 13:55                     ` Rainer Orth
2017-09-26 14:18               ` Pedro Alves
2017-09-26 14:21                 ` Pedro Alves
2017-10-03 13:01                   ` Rainer Orth
2017-09-29 11:53               ` Eli Zaretskii
2017-09-21 14:21 ` Pedro Alves [this message]
2017-09-21 14:23   ` Fix gdb 8.1 Solaris compilation 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=494a8b5e-a059-457c-61ad-f4edb2573a2c@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