[cl-debian] Bug#357144: libsigsegv_2.2-3(m68k/unstable/spice): ftbfs on m68k
Package: libsigsegv Version: 2.2-3 Severity: important libsigsegv fails to build from source due to a failed test. FWIW, I tested it with gcc-4.0 and it builds and tests fine. Here are selected excerpts from the buildd log. | Automatic build of libsigsegv_2.2-3 on spice by sbuild/m68k 85 | Build started at 20060315-1801 | ****************************************************************************** [...] | ** Using build dependencies supplied by package: | Build-Depends: debhelper (>> 4.0.0), autotools-dev, gcc-3.4 | Build-Conflicts: autoconf2.13, automake1.4 [...] | Checking correctness of source dependencies... | Toolchain package versions: libc6-dev_2.3.5-12 linux-kernel-headers_2.6.13+0rc3-2 gcc-4.0_4.0.2-9 g++-4.0_4.0.2-9 binutils_2.16.1cvs20060117-1 libstdc++6-4.0-dev_4.0.2-9 libstdc++6_4.0.2-9 [...] | Making check in tests | make[2]: Entering directory `/build/buildd/libsigsegv-2.2/tests' | /usr/bin/make check-TESTS | make[3]: Entering directory `/build/buildd/libsigsegv-2.2/tests' | Test passed. | PASS: sigsegv1 | FAIL: sigsegv2 | Starting recursion pass 1. | Stack overflow 1 caught. | Starting recursion pass 2. | Stack overflow 2 caught. | Test passed. | PASS: stackoverflow1 | Starting recursion pass 1. | Stack overflow 1 caught. | Starting recursion pass 2. | Stack overflow 2 caught. | Segmentation violation correctly detected. | Test passed. | PASS: stackoverflow2 | =================== | 1 of 4 tests failed | =================== | make[3]: *** [check-TESTS] Error 1 | make[3]: Leaving directory `/build/buildd/libsigsegv-2.2/tests' | make[2]: *** [check-am] Error 2 | make[2]: Leaving directory `/build/buildd/libsigsegv-2.2/tests' | make[1]: *** [check-recursive] Error 1 | make[1]: Leaving directory `/build/buildd/libsigsegv-2.2' | make: *** [build-stamp] Error 2 | ****************************************************************************** | Build finished at 20060315-1821 | FAILED [dpkg-buildpackage died] A full buildd log is available at <http://buildd.debian.org/build.php?pkg=libsigsegv&ver=2.2-3&arch=m68k> Other buildd logs may be available at <http://buildd.debian.org/build.php?arch=&pkg=libsigsegv> -- Stephen R. Marenka If life's not fun, you're not doing it right! <stephen@marenka.net>
Hi, On Wednesday 15 March 2006 22:37, Stephen R Marenka wrote:
libsigsegv fails to build from source due to a failed test. FWIW, I tested it with gcc-4.0 and it builds and tests fine.
Hmm. On x86 with gcc-4.0 it builds, but due to some bug the sigaltstack functions fail. Do you get checking for working sigaltstack... yes with gcc-4.0 on m68k? The older buildlog http://buildd.debian.org/fetch.php?&pkg=libsigsegv&ver=2.2-2&arch=m68k&stamp=1129725912&file=log&as=raw suggests not. If gcc-3.4 doesn't give a working version, maybe 3.3 does? The whole select the version that might work story with gcc is making me long for the 2.95 days ;-). Groetjes, Peter -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root, what is difference?" Pitr | "God is more forgiving." Dave Aronson|
On Thu, Mar 16, 2006 at 09:18:04AM +0100, Peter Van Eynde wrote:
Hi,
Howdy!
On Wednesday 15 March 2006 22:37, Stephen R Marenka wrote:
libsigsegv fails to build from source due to a failed test. FWIW, I tested it with gcc-4.0 and it builds and tests fine.
Hmm. On x86 with gcc-4.0 it builds, but due to some bug the sigaltstack functions fail. Do you get checking for working sigaltstack... yes with gcc-4.0 on m68k? The older buildlog http://buildd.debian.org/fetch.php?&pkg=libsigsegv&ver=2.2-2&arch=m68k&stamp=1129725912&file=log&as=raw suggests not.
Indeed, just as you say, it says no.
If gcc-3.4 doesn't give a working version, maybe 3.3 does?
I don't think 3.3 is going to be a release compiler.
The whole select the version that might work story with gcc is making me long for the 2.95 days ;-).
You and me both: gcc-4.0 has been nothing but a pain for m68k. Fortunately, gcc-4.1 has a yes for sigaltstack and builds successfully. Unfortunately, gcc-4.1 hasn't made it out of experimental yet. -- Stephen R. Marenka If life's not fun, you're not doing it right! <stephen@marenka.net>
Your message dated Thu, 13 Apr 2006 10:02:26 -0700 with message-id <E1FU5D8-0008VA-Qm@spohr.debian.org> and subject line Bug#357144: fixed in libsigsegv 2.2-5 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
participants (3)
-
owner＠bugs.debian.org -
Peter Van Eynde -
Stephen R Marenka