You are not logged in.

#1 2026-05-04 08:43:49

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,960

GNUstep discussing dropping gcc support

GNUstep is discussing its future .

One of the things that hurts them is that gcc-objc is stuck at version 1.0 and only llvm/clang supports objc2 (something to do with incompatible licenses).

Can a GNU project stop supporting GNU C Compiler and stay a GNU project or would that mandate leaving GNU ?

Should forcing 1 specific compiler be acceptable for opensource projects ?

Last edited by Lone_Wolf (2026-05-04 08:47:16)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#2 2026-05-04 15:49:20

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,133

Re: GNUstep discussing dropping gcc support

"Again?"
https://lists.nongnu.org/archive/html/d … 00090.html

I wouldn't say this is "forcing 1 specific compiler" and more exposing a (largely irrelevant) deficit in GCC lol
But if objc2 was incompatible w/ the GPL that should pose an existential problem. Is it?

Offline

#3 2026-05-05 08:17:23

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 14,960

Re: GNUstep discussing dropping gcc support

Obj-C licensing looks complicated but may not be a blocker. https://github.com/gnustep/libobjc2#history and https://en.wikipedia.org/wiki/Objective … mentations give some insight.

The libobjc2 runtime from gnustep can only be built by clang and is NOT usable for gcc at all.
If gnustep devs made libobjc2 mandatory today gnustep-base & gnustep-make would stop being buildable by gcc.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

Board footer

Powered by FluxBB