Carl Eugen Hoyos <ce@hoyos.ws> writes:
Dear Geoffrey!
Sorry for not writing any sooner, but since I don't read
gcc-patches often, I didn't see your mail and patch earlier.
It's absolutely wrong that the gnu-objc-runtime isn't working
properly on OSX!
I'm using it to compile (and run) gnustep-base library to do DO
messaging
with linux, solaris, irix and windows machines. I have two compilers
(actually more) on my system, (Apples) /usr/bin/gcc and gnu
/usr/local/bin/gcc, both work, and both have their objc-runtime (one
statically, one dynamically linked - so what?).
The gnu runtime runs absolutely nice:
You just have to link ln -s libobjc.a libobjc.dylib to
force the linker to use the statically linked gnu objc runtime lib.
PLEASE revert your patch, it doesn't make anything easier, but only
destroys a working feature!
Are you sure it really works? You aren't passing any special flags to
the compiler (like, say -fgnu-runtime)?
I think that by default, the compiler should work. You should not
need to pass special flags to the compiler just to make it work on
some system.
Have you tried building gnustep-base under the NEXT runtime?
Note that I said:
I wouldn't object to a patch that let you say
--enable-gnu-objc-runtime
(or whatever) and would both build the GNU runtime and change the
default,
if anyone wants to write one.