GNU bug report logs - #45817
28.0.50; Native fails

Previous Next

Full log

Message #76 received at 45817 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andrea Corallo <akrl <at> sdf.org>
Cc: 45817 <at> debbugs.gnu.org, kirill <at> korins.ky
Subject: Re: bug#45817: 28.0.50; Native fails
Date: Thu, 14 Jan 2021 16:04:54 +0200

> From: Andrea Corallo <akrl <at> sdf.org>
> Cc: "Kirill A. Korinsky" <kirill <at> korins.ky>, 45817 <at> debbugs.gnu.org
> Date: Thu, 14 Jan 2021 09:33:48 +0000
> 
> > Is this specific to macOS?
> >
> > In any case, if it's known that specific versions of GCC cause
> > problems on specific platforms, we should reject those versions (for
> > the libgccjit usage purposes) in configure, I think.
> 
> We do, not based on the version but (even better I think) we run a
> functional test at configure time.  The test use libgccjit to produce a
> shared, then this is loaded and used to ensure all the complete
> mechanism is functional.

Yes, but such tests can only verify that the basics work, whereas the
OP seemed to indicate that it generally works, but fails in some
subtle situation.  If libgccjit you are testing at configure time only
"mostly" works, you will be unable to detect that with simple tests.
For such subtly broken versions of libgccjit, we have no practical
means but looking at their version.

> I think in this specific case somenthing happend (maybe OS upgrade?) as
> when Emacs was compiled libgccjit clearly was working.

If that is the case, then there's no problem we need to solve here.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.