Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1306628 > unrolled thread
| Started by | Peter Hurley <peter@hurleysoftware.com> |
|---|---|
| First post | 2016-01-11 20:40 +0100 |
| Last post | 2016-01-11 21:50 +0100 |
| Articles | 4 — 2 participants |
Back to article view | Back to linux.kernel
s390 cross-compiling code coverage Peter Hurley <peter@hurleysoftware.com> - 2016-01-11 20:40 +0100
Re: s390 cross-compiling code coverage Peter Hurley <peter@hurleysoftware.com> - 2016-01-11 21:50 +0100
Re: s390 cross-compiling code coverage Guenter Roeck <linux@roeck-us.net> - 2016-01-11 22:00 +0100
Re: s390 cross-compiling code coverage Guenter Roeck <linux@roeck-us.net> - 2016-01-11 21:50 +0100
| From | Peter Hurley <peter@hurleysoftware.com> |
|---|---|
| Date | 2016-01-11 20:40 +0100 |
| Subject | s390 cross-compiling code coverage |
| Message-ID | <qPQtQ-6Lt-31@gated-at.bofh.it> |
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.
[toc] | [next] | [standalone]
| From | Peter Hurley <peter@hurleysoftware.com> |
|---|---|
| Date | 2016-01-11 21:50 +0100 |
| Message-ID | <qPRzz-7vv-3@gated-at.bofh.it> |
| In reply to | #1306628 |
On 01/11/2016 12:41 PM, Guenter Roeck wrote: > 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/ ? Hahaha, no. Because I never thought to look behind the html at kernel.org/pub/tools/crosstool which has _stale_ links to gcc 4.6.3 Thanks, Peter Hurley
[toc] | [prev] | [next] | [standalone]
| From | Guenter Roeck <linux@roeck-us.net> |
|---|---|
| Date | 2016-01-11 22:00 +0100 |
| Message-ID | <qPRJh-7Ao-11@gated-at.bofh.it> |
| In reply to | #1306680 |
On Mon, Jan 11, 2016 at 12:49:24PM -0800, Peter Hurley wrote: > On 01/11/2016 12:41 PM, Guenter Roeck wrote: > > 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/ ? > > Hahaha, no. Because I never thought to look behind the html at > > kernel.org/pub/tools/crosstool > > which has _stale_ links to gcc 4.6.3 > That is just to give people like me, who happened to find it, the opportunity to "shine" in public :-) Cheers, Guenter
[toc] | [prev] | [next] | [standalone]
| From | Guenter Roeck <linux@roeck-us.net> |
|---|---|
| Date | 2016-01-11 21:50 +0100 |
| Message-ID | <qPRzz-7vv-5@gated-at.bofh.it> |
| In reply to | #1306628 |
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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web