netdev - Re: [iproute PATCH 1/3] Use C99 style initializers everywhere

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 17 Jun 2016 17:21:26 -0700
From:	Stephen Hemminger <shemming@...cade.com>
To:	Phil Sutter <phil@....cc>
CC:	Daniel Borkmann <daniel@...earbox.net>,
	David Ahern <dsa@...ulusnetworks.com>,
	<netdev@...r.kernel.org>,
	Nicolas Dichtel <nicolas.dichtel@...nd.com>,
	"julien.floret@...nd.com" <julien.floret@...nd.com>
Subject: Re: [iproute PATCH 1/3] Use C99 style initializers everywhere

On Sat, 18 Jun 2016 02:02:21 +0200
Phil Sutter <phil@....cc> wrote:

> On Fri, Jun 17, 2016 at 11:57:53AM -0700, Stephen Hemminger wrote:
> > It makes sense that if you can build a kernel with old toolchain, that
> > iproute2 needs to be buildable as well.
> > 
> > The current kernels are documented to require 3.2 or later.  
> 
> So in your opinion we should stay compatible to gcc-3.2? Clarifying
> requirements like this one would make sense in order to know what to
> check against.


I want to have the least user complaints possible.
Since the main reason people build new iproute2 utilities is to work with features
of newer kernels. It makes sense to keep the requirements the same. Not sure if kernel
still builds with gcc-3.2, has anyone tried.