dann frazier wrote: > Same thing: OK. Another try with 1.20.0 this time? (http://snapshot.debian.org/archive/debian/20100524T154820Z/pool/main/g/gnustep-base/gnustep-base_1.20.0-1.dsc)
Upstream thinks this is either a GCC/libobjc issue exposed by the new -base code, or a serious problem in gnustep-base itself. As I can't reproduce the nefarious behavior on gcc61.fsffrance.org with a manually built GCC 4.4.4 from pristine source, I'm now building a new gcc with Debian patches. If I still can't reproduce, and 1.20.0 fails on Debian machines in the same way (which I suspect so), I'm afraid you or someone else from the hppa folks gotta take the hard road of bisecting... Upstream said: | My only new idea on how to proceed is to try a bisection of the code | changes since 1.19.3. You should start of by testing 1.20.0 and then | use SVN versions of the code in between. | | We have too much that changed since 1.19.3 to tell otherwise. The | whole thread and lock handling was completely rewritten, the | interaction with the Objective-C runtime was reimplemented, so were | NSInvocation and NSNumber. We enabled 64 bit NSInteger support and so | much more. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
