Re: libs-base fails to compile on OpenBSD

[Wolfgang Lux]

> Am 02.12.2018 um 18:12 schrieb Wolfgang Lux <address@hidden>:
> 
> 
> 
>> Am 02.12.2018 um 17:28 schrieb Riccardo Mottola <address@hidden>:
>> 
>> Sebastian Reitenbach wrote:
>>> What platform are you on? Why don’t you take the path the packages take and 
>>> use base clang, and libobjc2?
>> 
>> because libobjc2 I always have issues with that setup or clang or something.
>> 
>> I like to use GCC and its runtime.
>> 
>>> I definitely don’t recommend to use the system libobjc, at least you seem 
>>> to pick up system libobjc headers.
>> 
>> You have a point here, it is not picking up the correct headers - I am not 
>> using the system GCC but the one from packages (gcc 4.9) which is a perfctly 
>> fine runtime and which worked in OpenBSD 6.3 (as well as on many other 
>> systems, FreeBSD, Linux... etc)
>> 
>> With GCC no extra path is needed usually, it should just pick up "its own" 
>> runtime"
> 
> 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.

Or alternatively, we could make use of the hack I've added to gnustep-make 
years ago to allow compiling the gnu-gnu-gnu combo on macOS, which tries to 
find out the directory where the Objective-C runtime headers are installed and 
adds those to the compilation flags for C files.

Wolfgang