> No, just a packaging issue with somebody mentioning a static binutils build.
> That's when I saw the outdated version.
>
> Now updated in the GCC VCS.
OK, if you have updated the GCC sources, would you mind updating
the binutils-gdb.git as well? We should really keep the two as much
in sync as
On 23.11.2015 19:13, Joel Brobecker wrote:
In GCC zlib is only used for libjava; for binutils and gdb it is used when
building without --with-system-zlib. This just updates zlib from 1.2.7 to
1.2.8 (released in 2013). Applies cleanly, libjava still builds and doesn't
show any regressions in the
> In GCC zlib is only used for libjava; for binutils and gdb it is used when
> building without --with-system-zlib. This just updates zlib from 1.2.7 to
> 1.2.8 (released in 2013). Applies cleanly, libjava still builds and doesn't
> show any regressions in the testsuite. Ok to apply (even if we
On 11/22/2015 09:37 PM, Matthias Klose wrote:
In GCC zlib is only used for libjava; for binutils and gdb it is used
when building without --with-system-zlib. This just updates zlib from
1.2.7 to 1.2.8 (released in 2013). Applies cleanly, libjava still
builds and doesn't show any regressions in
On 23/11/15 04:37, Matthias Klose wrote:
> In GCC zlib is only used for libjava; for binutils and gdb it is used when
> building without --with-system-zlib. This just updates zlib from 1.2.7 to
> 1.2.8
> (released in 2013). Applies cleanly, libjava still builds and doesn't show
> any
> regre
In GCC zlib is only used for libjava; for binutils and gdb it is used when
building without --with-system-zlib. This just updates zlib from 1.2.7 to 1.2.8
(released in 2013). Applies cleanly, libjava still builds and doesn't show any
regressions in the testsuite. Ok to apply (even if we alrea
