This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Fix compilation of 64-bit gdb 7.7 on Solaris
- From: Rainer Orth <ro at CeBiTec dot Uni-Bielefeld dot DE>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: Pedro Alves <palves at redhat dot com>, gdb-patches at sourceware dot org
- Date: Fri, 07 Feb 2014 16:48:18 +0100
- Subject: Re: Fix compilation of 64-bit gdb 7.7 on Solaris
- Authentication-results: sourceware.org; auth=none
- References: <ydd7g98qkpl dot fsf at lokon dot CeBiTec dot Uni-Bielefeld dot DE> <52F3C017 dot 9040208 at redhat dot com> <ydd7g97dlbg dot fsf at lokon dot CeBiTec dot Uni-Bielefeld dot DE> <20140207153004 dot GH5485 at adacore dot com>
Hi Joel,
>> The patch has now been committed to mainline and the binutils 2.24
>> branch. Ok for gdb 7.7 branch now, too?
>
> Yep, with one request:
>
> All patches going to the branch following the first release now
> need to be documented in the Wiki. Examples from the previous
> release (See "Fixes in GDB 7.6.1"):
>
> https://sourceware.org/gdb/wiki/GDB_7.6_Release
no problem: can I just create a wiki account for myself, or need I be
added to some writers list? I remember at least the gcc wiki has added
some precautions after recent spam incidents.
> I apologize in advance for the extra work, but this means creating
> a PR for it, and then updating the release wiki by adding a reference
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?
And should I add the PR reference to the ChangeLog entry? It's not in
the mainline and binutils 2.24 checkins, obviously.
> 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.
> Thank you. And sorry again for the extra work. It just saves me a ton
> of time when producing corrective releases.
It's obviously easier have the committers do the work rather than the RM
reconstruct what they did :-)
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University