Re: Embedded blocks...

[Bertrand Dekoninck]

> Also, i dunno, but I think when a new architecture arises it may
> actually be easier to support it in llvm in the future...  I don't know
> why this would be more effort in clang than any other compiler.  In
> theory it should be less, cause it should be mostly llvm backend work.

I also think David wasn't serious when he said only Riccardo used the 
gcc runtime. I use it also on my ppc machines.
In fact, gnustep is packaged with the gcc-runtime on debian-based 
distros. It's quite a few users too. There should be some reasons why 
debian sticked to it. I don't know if there are plans to switch to 
libobjc2. Dropping support for gcc without talking to debian maintainers 
may put gnustep at risk of being deprecated as a whole.
libobjc2 doesn't run on ppc and big endian ppc64 (yes, those are legacy 
architectures) for now and I can't tell for others. I've tried many 
times on them, on linux and on freebsd, but I always fail for some 
reason. At least, we could have a decent clang version on these 
architectures now.

But I just miss the simplicity of the install of gnustep with the gcc 
runtime : basically, make install and it's running with no bugs. I
The install with libobjc2 has always been a kind of lottery on debian 
x86 (32 and 64 bits), dealing with the constantly evolving clang version 
requirements, now with the linker versions too, and with the bugs that 
sometimes arise with new versions. It's always cutting edge and not 
stable enough. Shouldn't this stabilize a little for distro maintainers ?

Bertrand