Re: lang/gcc14-devel fails to build for armv7: "You must select one and only one option from the BOOTSTRAP single"

From: Lorenzo Salvadore <developer_at_lorenzosalvadore.it>
Date: Tue, 24 Sep 2024 11:35:12 UTC
On Tuesday, September 24th, 2024 at 13:22, Lorenzo Salvadore <developer@lorenzosalvadore.it> wrote:

> 
> 
> On Tuesday, September 17th, 2024 at 18:43, Mark Millard marklmi@yahoo.com wrote:
> 
> > For example,
> > 
> > https://lists.freebsd.org/archives/freebsd-pkg-fallout/2024-September/652126.html
> > 
> > reports:
> > 
> > ---Begin OPTIONS List---
> > ====> You must select one and only one option from the BOOTSTRAP single
> > 
> > =====> No option was selected (and one must be)
> > 
> > *** Error code 1
> > 
> > Stop.
> > make: stopped making "showconfig" in /usr/ports/lang/gcc14-devel
> > 
> > . . .
> > 
> > =======================<phase: check-sanity >============================
> > 
> > ===== env: NO_DEPENDS=yes USER=root UID=0 GID=0
> > Making GCC 14.2.1.s20240831 for armv7-portbld-freebsd15.0 [c,c++,objc,fortran,jit]
> > ===> License GPLv3 GPLv3RLE accepted by the user
> > 
> > ====> You must select one and only one option from the BOOTSTRAP single
> > 
> > =====> No option was selected (and one must be)
> > 
> > *** Error code 1
> > 
> > Stop.
> > make: stopped making "check-sanity" in /usr/ports/lang/gcc14-devel
> > 
> > For reference:
> > 
> > It looks like this goes back to 2024-May or before, for all of:
> > 
> > 140releng-armv7-quarterly
> > 140releng-armv7-default
> > 132releng-armv7-quarterly
> > 132releng-armv7-default
> > 
> > (For other reasons over this time, until recently, builds of
> > main-armv7-default never completed the overall "bulk -a".
> > But main-armv7-default shows 2 recent examples, starting when
> > the armv7 jails on ampere2 were updated to a vintage that had
> > the fix for that more overall problem for main.)
> 
> 
> Thanks for your report. Does the attached patch fix the issue?
> 
> Cheers,
> 
> Lorenzo Salvadore

Hmm... Looking at the other thread about lang/gcc14 I believe the issue
is more complicate. I will likely open a bug report on bugzilla to track
both issues (otherwise the emails will get lost somewhere in my inbox and
I will forget about them).

Cheers,

Lorenzo Salvadore