[Bug libobjc/11572] [3.3/3.4/3.5 regression]: GNU libobjc no longer compiled on Darwin

["cehoyos at ag dot or dot at" <gcc-bugzilla at gcc dot gnu dot org>]

------- Additional Comments From cehoyos at ag dot or dot at  2004-03-23 18:48 -------
(In reply to comment #17)
Thank you, Andrew, for your answer.
It's true that it's not easy to use one compiler for both runtimes. (Not
thinking of copyrights, would "merging" of the headers with #ifdef wrappers make
it easier?) But that's not that important anyway: Apple ships (shipped?) its
systems with two compilers (gcc and gcc3), so why not adding a third one? As
long as it's not configured with --prefix=/usr that shouldn't make problems, and
I would never do this on any system! (This prefix definitely screwed up OSX
development environments up to the released version of 3.3.3, does it work with
3.4?)

And since the gnu runtime comes as a static library, the runtime will never be
the problem after adding the symbolic link libobjc.dyld to libobjc.a. It's true
that this didn't work out of the box, but adding a symbolic link is far easier
than fiddling around with the configure scripts! (One often has to add a symblic
link to /usr/local/bin after installation anyway.)

That's why I still can't see why this patch was such a good idea. It did
introduce a regression! Why not having a configuration option
--enable-gnu-runtime (which adds the symbolic link after installation and makes
the gnu-runtime standard for the preprocessor)? The standard on darwin would
then be to configure without this option.

I really hope that the difficult and obviously longlasting (and impossible?)
task to merge the runtimes won't be the reason that compiling for the
gnu-runtime on darwin will be far more difficult in future!

Thanks, Carl Eugen Hoyos

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11572