On Fri, Feb 04, 2022 at 09:44:26PM +0000, Daniel Bungert wrote: > Package: icmake > Version: 10.01.01-2 > Severity: normal > X-Debbugs-Cc: daniel.bung...@canonical.com
Hi Daniel, hi Frank: I have access to a s390x porterbox and can reproduce the build failure, even with a patched version of icmake. Thus, I have reopened the bug and I do think that the issue lies with icmake, although I think it's something else. It's not even attempting to start the build. I added the -V switch to bobcat's top-level ./build shebang to see how far it's getting, and the answer is "not very." The next line of output below should be the build starting but instead it exits with with return code 0. (sid_s390x-dchroot)tmancill@zelenka:~/bobcat/bobcat-5.09.01$ ./build libraries all calling `/usr/libexec/icmake/icm-pp ./build /tmp/6393usq56W' calling `/usr/libexec/icmake/icm-comp /tmp/6393usq56W /tmp/6393.bim.6QGCyE' calling `/usr/libexec/icmake/icm-exec /tmp/6393.bim.6QGCyE' I'm attaching the output of an strace of the same command above in case something stands out to either of you. My next step is to install debugging symbols for icmake and run under gdb, but I won't be able to try that until tomorrow. Cheers, tony
bobcat_icmake_strace.out.gz
Description: application/gzip
