Re: FreeBSD / libobj2 issue after update - all apps crash

[Riccardo Mottola]

Hi,


David Chisnall wrote:
> On 04/06/2019 09:46, Riccardo Mottola wrote:
> > Hi David,
> >
> > David Chisnall wrote:
> > > Thanks for the report.  Please can you file an issue on GitHub?  
> > > This is a quite surprising error - it implies that either clang has 
> > > a bug or that something is trying to manually create or modify 
> > > protocols without calling through the runtime.  This might happen if 
> > > you have a version of GNUstep compiled against the gcc runtime and 
> > > using ObjectiveC2.framework instead of the runtime's public APIs, 
> > > but that shouldn't be the case with the packaged versions.
> >
> > clang and libobjc2 are packaged, however gnustep installation is 
> > compiled by my by current sources. I did not do anything special, I 
> > configured make with:
> >
> > $ ./configure --prefix=/ --with-layout=gnustep 
> > CFLAGS=-I/usr/local/include
>
> Are you using -make from packages, which will be configured to use the 
> new ABI?


no, I am using everyghing from git HEAD of our repositories, including 
latest gnustep make.
Do you pass some special configuration parameters when packaging? I can 
attempt that.


> Okay, this is not one that will be used by -make from packages, 
> because it doesn't support the 2.0 ABI.  Please use the clang from the 
> llvm7 or lllv8 package, or from the base system in 12.  It looks as if 
> you're using the old (GCC) ABI, which may mean that you've linked in 
> the ObjectiveC2 framework and are explicitly constructing internal 
> runtime data structures from an old version of the runtime.  Please 
> can you check where the invalid protocol is coming from?  It may also 
> be something that we're failing to correctly upgrade when using the 
> legacy ABI.

Ok, so it is an older compiler, but should not the runtime support it? 
there are no two libobjc2 packages, or is libobjc2 no longer compatible 
with the GCC runtime?

How can I check for the protocol? It is coming "from inside GNUstep" 
since I just installed core packages and then am running Ink, so there 
is no custom code of mine.
Maybe we just have some issue in gnustep which we didn't discover.

When you say "upgrade" are you referring to FreeBSD package upgrade or 
GNUstep ?

Indeed, on another computer where I am running FreeBSD 12 instead, 
everything worked out of the box.

Riccardo