Hi Wolfgang,
Wolfgang Lux wrote:
I haven't been using OpenBSD for years, so I'm not sure why there is an
/usr/include/objc header directory that does not match the compiler. But
anyway, this is a problem that you'll see on every system where you use a gcc
version which does not match the default compiler. Gcc knowns about the special
directory containing the Objective-C headers and includes that in the default
search path. However, that applies only to Objective-C files and not to plain C
files like runtime.c. I think the best way to move forward would be renaming
runtime.c into runtime.m so that this file gets compiled with the correct
search path.
it could be a trick... I think here it is a little more awkward,
however: the "pkg" gcc is in its own directory:
/usr/local/lib/gcc/i386-unknown-openbsd6.4/4.9.4/include/objc/objc.h
The system gcc, is system-wide in the search path:
/usr/include/objc/objc.h
Now, I suppose the GCC trick is that including "objc.h" works correctly.
However, if you include objc-api.h, which does not exist anylonger in
more recent versions of gcc, it will include the "Old" one because it is
the only one and it is in a valid search path, do you get my reasoning?
I think we should include the "right" system headers in runtime, perhaps
some should not be included or we should have some sort of "if gcc < XX"
include one set, else other set (I don't know which version9.
Instead, we check header-per-header and "somewhere" they will be found
and then pulled in.
I am sure thus your .m trick would work?
Riccardo
_______________________________________________
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev
