linux-kernel - s390 cross-compiling code coverage

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-next>] [day] [month] [year] [list]

Date:	Mon, 11 Jan 2016 11:38:35 -0800
From:	Peter Hurley <peter@...leysoftware.com>
To:	Heiko Carstens <heiko.carstens@...ibm.com>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	linux-s390@...r.kernel.org
Cc:	Linux kernel <linux-kernel@...r.kernel.org>
Subject: s390 cross-compiling code coverage

Occasionally, it's necessary to touch s390 code because of changes
within a subsystem, such as tty/serial.

Since changing the configs to the zEC12 march, the gcc 4.6.3 s390
cross-compiler hosted at kernel.org/pub/tools/crosstool no longer
builds any of the configs.

Would someone please add a config expected to build with that
cross-compiler? And/or point to a more recent cross-compiler?
And either confirm that one of these configs is suitable for
build coverage?

Regards,
Peter Hurley

PS - I did make sure that recent changes I've submitted for s390 drivers
     build, by hand-configuring from default_defconfig, but I'd like
     to rely on automation for build testing.