Hi, during the build of the new scummvm release we run into the following build issue: https://koji.fedoraproject.org/koji/getfile?taskID=3507060&name=build.log + /usr/lib/rpm/find-debuginfo.sh --strict-build-id /builddir/build/BUILD/scummvm-1.4.0 extracting debug info from /builddir/build/BUILDROOT/scummvm-1.4.0-1.fc16.i386/usr/bin/scummvm Stabs debuginfo not supported: /builddir/build/BUILDROOT/scummvm-1.4.0-1.fc16.i386/usr/bin/scummvm error: Bad exit status from /var/tmp/rpm-tmp.wtAmWB (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.wtAmWB (%install) Child returncode was: 1 EXCEPTION: Command failed. See logs for output. It looks like that the compiled binary contains STABS debug symbols. I have investigated this problem and indeed the nasm assembler will generate by default STABS instead of DWARF debug symbols. According to https://bugzilla.redhat.com/show_bug.cgi?id=725378#c16 rpmbuild has now the following behavior: F17: rpmbuild will issue a warning but not fail the build F15, F16: rpmbuild will fail the build once it detects STABS debug symbols in the binaries I'm wondering what would be the best solution here: a) apply a patch to the package to let nasm generate DWARF debug symbols (and probably propose this patch upstream) b) change the behavior of rpmbuild in F15 and F16 to not treat these errors as fatal c) file a bug against nasm to change the default debug symbol format to DWARF in case of compiling for the ELF target Probably it would even make sense to do all 3 of them. Best regards, Christian -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
