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.
Quoted 12 lines · Peter Hurley
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
Quoted 15 lines · Guenter Roeck
Quoted 12 lines · Peter Hurley
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,
Quoted 7 lines
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_Z196withCONFIG_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
Quoted 21 lines · Peter Hurley
Quoted 20 lines · Guenter Roeck
Quoted 12 lines · Peter Hurley
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_Z196withCONFIG_MARCH_Z900.
Quoted 9 lines
Quoted 2 lines
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