From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Fix gdb 8.1 Solaris compilation
Date: Thu, 21 Sep 2017 14:23:00 -0000 [thread overview]
Message-ID: <yddpoakp1u2.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <494a8b5e-a059-457c-61ad-f4edb2573a2c@redhat.com> (Pedro Alves's message of "Thu, 21 Sep 2017 15:21:08 +0100")
Hi Pedro,
> 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.)
I do, but am working with hg locally since I always found git to be a
total nightmare.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
prev parent reply other threads:[~2017-09-21 14:23 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 ` Fix gdb 8.1 Solaris compilation Pedro Alves
2017-09-21 14:23 ` Rainer Orth [this message]
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=yddpoakp1u2.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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