On 02.10.2025 12:34, R Frith-Macdonald wrote:
On 02/10/2025 11:18, Andreas Fink via Discussion list for the GNUstep
programming environment wrote:
On 02.10.2025 11:57, R Frith-Macdonald wrote:
I suppose your problem might be that you are using the more recent
2.2 ABI but the default is specifying the 2.0 ABI?
You can override the default using --with-runtime-abi configuration
option.
Thanks for that hint. Indeed I use the latest libobjc2.2.1. I'm
surprised the ABI has changed.
would that mean -fobjc-runtime=gnustep-2.0 has to be changed
to -fobjc-runtime=gnustep-2.2.1 as well?
I don't actually know about that (I'm not using the latest libobjc);
it was just a secondary suggestion that there might be an issue with
the latest runtime version.
My *best* buess woulkd be my first suggestion:
From your description, this appears to be gnustep-make doing the
correct thing (-DGNUSTEP_RUNTIME=1 means the new runtim,e is in use),
and the issue would be in the 'subsequent code'
That is, your output suggests that gnustep-make is doing the right
thing, and certainly defining GNUSTEP_RUNTIME=1 is correct for using
the new runtime (ie NOT the GNU one that comes with GCC).
well base/gui/back/corebase now compiles and install
now my own configure.ac makes strange things. it fails at the check for
cross compilation
reproducing that test by hand fails that it fails after including
Foundation/Foundation.h that it doesnt know about things like NSArray etc
interestingly if I call ./configure with --host
aarch64-unknown-linux-gnu which is the architecture I'm running on. it
deso not fail which i find puzzling.
But whats not puzzling with autotools :)
