Hi Riccardo,
> The base configure script reports:
>
> checking the Objective-C runtime... GNU
> checking for custom shared objc library... NONE
> checking objc/runtime.h usability... yes
> checking objc/runtime.h presence... yes
> checking for objc/runtime.h... yes
> checking objc/objc.h
Hi Wolfgang,
Wolfgang Lux wrote:
Am 18.12.2018 um 22:01 schrieb Riccardo Mottola :
Making all for subproject ObjectiveC2...
Compiling file runtime.c ...
runtime.c:35:27: fatal error: objc/objc-api.h: No such file or directory
#include
^
compilation terminated.
> Am 18.12.2018 um 22:01 schrieb Riccardo Mottola :
>
> Making all for subproject ObjectiveC2...
> Compiling file runtime.c ...
> runtime.c:35:27: fatal error: objc/objc-api.h: No such file or directory
> #include
> ^
> compilation terminated.
>
>
> which is
Hi Fred,
Fred Kiefer wrote:
Riccardo,
you seem to be missing out on the underlying problem that Wolfgang tried to
explain. For the GNUstep base library there are two cases which are supported.
Either a new Obj-C runtime is installed on your machine then this gets used and
the GNUstep
> Am 18.12.2018 um 00:55 schrieb Riccardo Mottola :
> Wolfgang Lux wrote:
>> To be honest, no. The runtime.c file unconditionally includes objc-api.h, so
>> it's obviously not supposed to compiled with a compiler that lacks the
>> objc-api.h header file. So it doesn't really matter if the
Hi Wolfgang,
Wolfgang Lux wrote:
To be honest, no. The runtime.c file unconditionally includes objc-api.h, so
it's obviously not supposed to compiled with a compiler that lacks the
objc-api.h header file. So it doesn't really matter if the compiler would find
the header from a different
> Am 05.12.2018 um 10:38 schrieb Riccardo Mottola :
>
> 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
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
> Am 02.12.2018 um 18:12 schrieb Wolfgang Lux :
>
>
>
>> Am 02.12.2018 um 17:28 schrieb Riccardo Mottola :
>>
>> 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
> Am 02.12.2018 um 17:28 schrieb Riccardo Mottola :
>
> 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
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
Hi
Sent from my iPhone
> On 2. Dec 2018, at 14:30, Riccardo Mottola wrote:
>
> Hi,
>
> I just upgraded OpenBSD to 6.4, including all packages.
> The compiler did not change in revision, I guess it was just updated, so gcc
> is still 4.9 from ports.
>
> I recompile GNUstep from scratch and
Hi,
I just upgraded OpenBSD to 6.4, including all packages.
The compiler did not change in revision, I guess it was just updated, so
gcc is still 4.9 from ports.
I recompile GNUstep from scratch and it fails:
Compiling file runtime.c ...
In file included from runtime.c:35:0:
13 matches
Mail list logo
