Steve, as far as I can trace the problem it appears to be in src/setjmp/setjmp.c:
/* Why use K&R syntax here? setjmp() is often a macro and that expands into a call to, say, __setjmp() and we need to define the libunwind-version of setjmp() with the name of the actual function. Using K&R syntax lets us keep the setjmp() macro while keeping the syntax valid... This trick works provided setjmp() doesn't do anything other than a function call. */ with FORTIFY_SOURCE, unfortunately setjmp is no longer a function call, but rather _setjmp. I haven't found a way to disable the portion of FORTIFY_SOURCE which remaps setjmp to _setjmp specifically (_FORTIFY_SOURCE=1 doesn't do the trick), and I have slight doubts that there's one. At least, if there's one it's undocumented ;). Any pointers or would an upload as proposed by Stephan be adequate for maverick? -- libunwind ftbfs on amd64 and i386 https://bugs.launchpad.net/bugs/522106 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
