The -Wbounded warning is caused by somewhat strange and conflicting
definitions for FILNMLEN/E_FILNMLEN in coff/*.h. Unless anyone cares
about long NT filenames, I think we should just remove support for those
until the gdb/bfd people sort this out and make the defines consistent.
It probably wo
On Sat, Oct 15, 2011 at 03:37:16PM +0200, Pascal Stumpf wrote:
> The -Wbounded warning is caused by somewhat strange and conflicting
> definitions for FILNMLEN/E_FILNMLEN in coff/*.h. Unless anyone cares
> about long NT filenames, I think we should just remove support for those
> until the gdb/bfd
On Sat, 15 Oct 2011 17:09:32 +0200, Marc Espie wrote:
> On Sat, Oct 15, 2011 at 03:37:16PM +0200, Pascal Stumpf wrote:
> > The -Wbounded warning is caused by somewhat strange and conflicting
> > definitions for FILNMLEN/E_FILNMLEN in coff/*.h. Unless anyone cares
> > about long NT filenames, I thi
On Sat, 15 Oct 2011 18:02:06 +0200, Pascal Stumpf wrote:
> On Sat, 15 Oct 2011 17:09:32 +0200, Marc Espie wrote:
> > On Sat, Oct 15, 2011 at 03:37:16PM +0200, Pascal Stumpf wrote:
> > > The -Wbounded warning is caused by somewhat strange and conflicting
> > > definitions for FILNMLEN/E_FILNMLEN in
On Sat, 15 Oct 2011 18:56:25 +0200, Pascal Stumpf wrote:
> On Sat, 15 Oct 2011 18:02:06 +0200, Pascal Stumpf wrote:
> > On Sat, 15 Oct 2011 17:09:32 +0200, Marc Espie wrote:
> > > On Sat, Oct 15, 2011 at 03:37:16PM +0200, Pascal Stumpf wrote:
> > > > The -Wbounded warning is caused by somewhat stra
On Sat, 15 Oct 2011 19:33:22 +0200, Pascal Stumpf wrote:
> Oh, and I just checked: This bug even is in src binutils (both 2.15 and
> 2.17), just nobody noticed because -Werror isn't used there (but it
> probably should be fixed there too, right?).
>
>
Upstream fix is here. Attached are patches
On Tue, Oct 25, 2011 at 06:13:11PM +0200, Pascal Stumpf wrote:
> On Sat, 15 Oct 2011 19:33:22 +0200, Pascal Stumpf wrote:
> > Oh, and I just checked: This bug even is in src binutils (both 2.15 and
> > 2.17), just nobody noticed because -Werror isn't used there (but it
> > probably should be fixed