From: Guenter Roeck <linux@roeck-us.net>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-s390@vger.kernel.org,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: s390 cross-compiling code coverage
Date: Mon, 11 Jan 2016 12:41:12 -0800 [thread overview]
Message-ID: <20160111204112.GA4260@roeck-us.net> (raw)
In-Reply-To: <569404BB.1010008@hurleysoftware.com>
On Mon, Jan 11, 2016 at 11:38:35AM -0800, Peter Hurley wrote:
> 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?
>
Hi Peter,
Seems to still work for me (up to and including linux-next), at least
for building defconfig, allmodconfig, and allnoconfig. Also, the defconfig
kernel boots for me with qemu after replacing CONFIG_MARCH_Z196 with
CONFIG_MARCH_Z900.
Have you tried gcc 4.9.0 from
www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.9.0/ ?
Guenter
next prev parent reply other threads:[~2016-01-11 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 19:38 s390 cross-compiling code coverage Peter Hurley
2016-01-11 20:41 ` Guenter Roeck [this message]
2016-01-11 20:49 ` Peter Hurley
2016-01-11 20:57 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160111204112.GA4260@roeck-us.net \
--to=linux@roeck-us.net \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--cc=schwidefsky@de.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox