This is the mail archive of the
mailing list for the binutils project.
Re: Binutils 2.26 released
- From: Tristan Gingold <gingold at adacore dot com>
- To: Mike Frysinger <vapier at gentoo dot org>
- Cc: Matthias Klose <doko at ubuntu dot com>, binutils <binutils at sourceware dot org>
- Date: Mon, 1 Feb 2016 11:32:22 +0100
- Subject: Re: Binutils 2.26 released
- Authentication-results: sourceware.org; auth=none
- References: <9F317B17-DC7C-42A1-A3BD-89E7A349FAE5 at adacore dot com> <56A8FC25 dot 6060503 at ubuntu dot com> <B1E0E267-CBE4-48FA-8FC1-DC4BC1229255 at adacore dot com> <20160128163707 dot GZ14840 at vapier dot lan>
> On 28 Jan 2016, at 17:37, Mike Frysinger <email@example.com> wrote:
> On 28 Jan 2016 09:54, Tristan Gingold wrote:
>>> On 27 Jan 2016, at 18:19, Matthias Klose <firstname.lastname@example.org> wrote:
>>> On 27.01.2016 10:25, Tristan Gingold wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>> I am pleased to announce binutils 2.26. You can get it from sourceware.org
>>>> and ftp.gnu.org in the usual places, e.g. ftp://ftp.gnu.org/gnu/binutils/.
>>> However, the release doesn't set back the development mode to release. At least bfd/development.sh is still set to true, causing the date included in the sonames. Is anything else affected?
>> Indeed, I have forgotten that.
> will there be a respin or bump or something ? this is a fix that
> everyone trying to build/ship binutils will need to make â
Apparently there is already a couple of fixes to backport in 2.26, so it is highly possible that a new 2.26 release will be created.