Re: Armv7 buildworld puzzle (jaillex.c:850:1: error: declaration shadows a variable in the global scope [-Werror,-Wshadow])

Ronald Klop <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <1551701372.2470.1737710647523@localhost>
Hi Bob,

I guess a make clean or rm -rf /usr/obj/* might help.

NB: I can't imagine the error does not say 'which variable' is shadowed. It helps the readers of your mail to copy-paste a little more context.

Regards,
Ronald.

 
Van: "Herbert J. Skuhra" <[email protected]>
Datum: vrijdag, 24 januari 2025 08:04
Aan: [email protected]
Onderwerp: Re: Armv7 buildworld puzzle
> 
> On Thu, Jan 23, 2025 at 05:14:25PM -0800, bob prohaska wrote:
> > An attempt to build world on armv7 (PI2 v1.1) keeps getting stuck with:
> > jaillex.c:850:1: error: declaration shadows a variable in the global scope [-Werror,-Wshadow]
> >
> > Repeat git pulls find no updates related to jailex.c and find does not discover
> > any file in /usr/src by that name.
> >
> > Git status reports
> >
> > On branch stable/14
> > Your branch is up to date with 'freebsd/stable/14'.
> >
> > Untracked files:
> >   (use "git add <file>..." to include in what will be committed)
> >         buildscript
> >         buildworld.log
> >         installscript
> >
> > I'm mystified, first at the build stoppage and second by the file being
> > named and quoted but not find-able.
> >
> > The system isn't valuable, but if there's an easy fix or workaround
> > I'd like to try it. The system started life as 12.4. Sources were
> > replaced with stable/14, a new kernel was built and runs seemingly
> > ok. To have buildworld fail past the "building everything" mark with
> > a complaint quoting a file that's not visible is quite baffling.
> 
> There are
> 
> /usr/src/usr.sbin/jail/jaillex.l
> and
> /usr/obj/usr/src/arm64.aarch64/usr.sbin/jail/jaillex.c
> 
> The latter is autogenerated during the build.
>  
> 
> 
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.