Re: Warning with clang, error with gcc : attached files

[Bertrand Dekoninck]

On 2019-05-01 10:04:55 +0200 David Chisnall 
<gnustep@theravensnest.org> wrote:

> On 30/04/2019 21:45, Bertrand Dekoninck wrote:
> > If only I could... but Objc2 is still no an option on ppc linux and
> > that's precisely why I want to port rik to objc1.
>
> Making Objective-C 2 work on PowerPC is almost certainly less effort 
> than 
> porting a codebase to an old dialect and maintaining a less 
> maintainable 
> fork.  If you're happy with the slow message send paths (no 
> objc_msgSend, 
> just the old objc_msg_lookup then call the resulting IMP) and you're 
> not 
> using imp_implementationWithBlock then it should all work already, 
> modulo 
> build system issues.

I'd certainly be happy with it. The last time I tried (over a year 
from now), the problem was a linker issue I could not resolve in 
Debian Jessie. And it was a hassle. I don't have the knowledge to deal 
with this kind of issues.

I'm eager to upgrade it to Debian unstable because there is a work in 
progress to have it easily installable on macs.

I have here a powerbook G4 with a stable debian jessie, a good working 
browser (Articfox) and a working gcc gnustep install which is my 
day-to-day desktop. It works like a charm, really.

I may try another time someday to build libobjc2 but not on this 
machine. But the more I wait, the more difficult to get are the 
dependancies (clang for instance, is constantly moving from a version 
to another). I'm not sure I would try with the new api of libobjc2 
because I really don't want to build clang by myself. For now, objc1 
does seem to be a sustainable effort to me while objc2 doesn't, sorry.

Cheers, Bertrand