Re: Panic while making buildlernel on RPi3

On Fri, Mar 04, 2022 at 10:51:00PM -0800, Mark Millard wrote:
> On 2022-Mar-4, at 20:30, bob prohaska <fbsd@www.zefox.net> wrote:
> 
> > On Fri, Mar 04, 2022 at 05:36:20PM -0800, Mark Millard wrote:
> 
> Are you going to do the official-builds-on-microsd-card
> sorts of boot and try tests that I've suggested, such as a
> 13.1-PRERELEASE (snapshot) test? (This avoids your having
> built anything tested and all but whatever minimal
> configuration that you need to do to allow the test.)
>
Yes, after stable/13 settles down a bit. This failure was on
-current. 

> Getting a failure from such an installation of official
> installation materials might be more likely to lead to
> getting help isolating the issue. 

Understood. At this point I have two RPI3 systems which
exhibit the same problem (faulty ping response). One has
followed stable/13 (which had the clang errors you helped
with), the other has tracked -current.  
 
> [Back to the Subject line's issue . . .]
> 
> > I've been using -DWITH_META_MODE as a default setting for buildworld and 
> > buildkernel. Might this be part of my  problems with the Pi3's ? 
> 
> NO_CLEAN is more likely to have the result messed up: it
> does less dependency checking and can miss more that should
> be rebuilt/relinked.
> 
> WITH_META_MODE is likely to rebuild more than NO_CLEAN, and
> so, less likely to include stale material.
> 
> Without special knowledge of the details of what all needs to
> be rebuilt at the time, WITH_META_MODE is normally safer.

I note with interest that you say "safer", not safe. How do the
various cleaning targets described in the build manpage compare?
There's clean, cleandir and cleandepend, along with rm -rf /usr/obj.
It appears cleandir run twice is equivalant to combined clean and
rm -rf /usr/obj. I've not tried cleandepend yet, might it help?

It sounds like an occasional clean start buildworld/buildkernel
would reduce uncertainty, if not problems. 

Thanks very much for writing!

bob prohaska