From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: Fix compilation of 64-bit gdb 7.7 on Solaris
Date: Mon, 10 Feb 2014 15:47:00 -0000 [thread overview]
Message-ID: <yddppmvc6mg.fsf@lokon.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <20140207171942.GI5485@adacore.com> (Joel Brobecker's message of "Fri, 7 Feb 2014 21:19:42 +0400")
Hi Joel,
> I'd like us to have ACLs as well for the GDB wiki, but I haven't had
> time to work on that, yet. So you should be able to edit as soon as
> you have an account.
right, worked just fine.
>> More questions here: this is actually a bfd issue, but neither binutils
>> nor gdb has a component for that. I could file it under gdb/build,
>> though. Btw., bugzilla currently lacks the gdb 7.7 version. Could you
>> please add that, too?
>
> Sure, gdb/build sounds fine to me.
>
> Regarding gdb-7.7, I'll have to ask Tom. In the meantime, can you
> set the field to "HEAD"? I'll change it once the new version is added.
Since I could file the PR only today, I could use the new 7.7 version.
>> And should I add the PR reference to the ChangeLog entry? It's not in
>> the mainline and binutils 2.24 checkins, obviously.
>
> If you don't mind. I don't know whether they'll want it for binutils
> 2.24. For master, if you don't mind updating the ChangeLog (no need
> to send a patch), that'd be great.
I've done it for mainline, not yet for the binutils 2.24 branch.
>> > to this fix. I will prepare the wiki page by adding a section for 7.7.1
>> > where you'll be able to document your fix.
>>
>> Ok. Please let me know once the page is there. I'll wait with the
>> commit until then.
>
> It's done :).
I've now filed the PR (build/16550), applied the patch to the gdb 7.7
branch and updated the mainline ChangeLog with the PR reference.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2014-02-10 15:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 16:17 Rainer Orth
2014-02-06 17:02 ` Pedro Alves
2014-02-07 10:07 ` Rainer Orth
2014-02-07 14:55 ` Rainer Orth
2014-02-07 15:29 ` Pedro Alves
2014-02-07 15:30 ` Joel Brobecker
2014-02-07 15:48 ` Rainer Orth
2014-02-07 17:19 ` Joel Brobecker
2014-02-07 20:44 ` Tom Tromey
2014-02-10 15:47 ` Rainer Orth [this message]
2014-02-11 2:20 ` Joel Brobecker
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=yddppmvc6mg.fsf@lokon.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=brobecker@adacore.com \
--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