Benjamin Kaduk <ka...@mit.edu> writes: > The longjump error is going to be coming from src/lwp/process.o, which > is compiled from either verious assembly files or a C file depending on > the architecture. I don't have any sparc-linux systems, so I won't be > able to do any direct diagnosis of this issue (which is almost certainly > sparc-linux-specific). From the build log, it looks like the C version > is being used here; there haven't been any changes to that file in > upstream between 1.6.1 and 1.6.9. We don't have any Debian-specific > patches to that file, either. (In fact, we didn't have any Debian > patches at all for 1.6.10~pre1.)
Another possibility is glibc changing something about what it expects. It wouldn't be the first time that LWP has been broken by changes to glibc even when there was no source changes to LWP itself. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
