On 12 Aug 2014, at 09:28, David Chisnall <thera...@sucs.org> wrote: > > The bug is in the GCC Objective-C runtime. The runtime is responsible for > ensuring that +initialize is thread safe. The 'fix' is to use the GNUstep > runtime as well. Is there a reason why you're using GCC for Objective-C code?
But the problem in the gnu runtime was fixed in May 2011 And gcc-4.6.3 was released in March 2012 So in this case it seems that the user must have actually configured/built gnustep with a runtime/compiler older than the one they said they used . Perhaps they configured it with one runtime/compiler and then switched to a more recent one but didn't reconfigure/rebuild gnustep-base after the change. _______________________________________________ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
