Re: llvm10 build failure on Rpi3

From: bob prohaska <fbsd_at_www.zefox.net>
Date: Fri, 25 Jun 2021 20:52:34 -0700
On Fri, Jun 25, 2021 at 07:52:32PM -0700, Mark Millard wrote:
[huge snip, hope the quotes are still correct]
> > So I'm going to suggest using an official kernel build
> > as built by the ci.freebsd.org systems, one that is not
> > GENERIC-MMCCAM. In:
> > 

World and kernel are updating now to -current as of yesterday.
I'll replace GENERIC-MMCCAM with GENERIC for simplicity.


> > 
> > I gather that no RPi4B is available to move the media
> > to? (Having more RAM but being able to force much of
> > it to be ignored can be handy as a test environment
> > for this kind of context.)
> >
 
It's still patiently chewing away at www/chromium single-threaded.
My mistake, but best to finish what's started.. Now that how to
use the packages created is known they can be tested. 

> 
> So: no warning about being mis-tuned vs. the 1 GiByte of
> used RAM. (I do not know about your context for this.)
> 

My Pi3 does report too much swap. But I remain uncertain about
the practical significance of the warning. I gather the issue
is that a certain amount memory is set aside to "index", for
lack of a better word, the data stored in swap. If there's too
much swap relative to index, not all swap can be used. That
seems not much different than running out of swap. 

> All the ports that devel/llvm10 needs are already in place
> for poudriere's use for this experiment.
> 
> Another point is:
> 
> # more /usr/local/etc/poudriere.d/options/devel_llvm10/options 
> # This file is auto-generated by 'make config'.
> # Options for llvm10-10.0.1_3
> _OPTIONS_READ=llvm10-10.0.1_3
> _FILE_COMPLETE_OPTIONS_LIST=BE_AMDGPU CLANG DOCS EXTRAS LIT LLD LLDB LLD_LINK OPENMP PYCLANG BE_FREEBSD BE_NATIVE BE_STANDARD
> OPTIONS_FILE_SET+=BE_AMDGPU
> OPTIONS_FILE_SET+=CLANG
> OPTIONS_FILE_SET+=DOCS
> OPTIONS_FILE_SET+=EXTRAS
> OPTIONS_FILE_SET+=LIT
> OPTIONS_FILE_SET+=LLD
> OPTIONS_FILE_SET+=LLDB
> OPTIONS_FILE_SET+=LLD_LINK
> OPTIONS_FILE_SET+=OPENMP
> OPTIONS_FILE_UNSET+=PYCLANG
> OPTIONS_FILE_UNSET+=BE_FREEBSD
> OPTIONS_FILE_SET+=BE_NATIVE
> OPTIONS_FILE_UNSET+=BE_STANDARD
> 
> (So I normally build less than BE_STANDARD or
> BE_FREEBSD would build.)

I'm my own worst enemy when it comes to customization.
The less changed the better 8-)
 
> We will see if this is enough common context to
> replicate the general type of build problem.
> (Your details very from one attempt to the next
> so an exact match need not be expected, even if
> if this does also fail.)
>

If you replicate the problem I'll be very pleased.
And just slightly relieved.

My suspcions still center around  things I might have 
done to corrupt /usr/local/poudriere. That leaves
me wondering how to proceed after world, kernel and ports
are updated. Delete /usr/local/poudriere (which would toss
the packages created so far), delete only the jail (not
sure if that'll delete existing packages library) or 
something more selective that I don't know about? 

The Pi3B is purely experimental, but I'd rather not throw 
away usable progress given the extreme slowness of that
progress. 

Thank you!

bob prohaska
Received on Sat Jun 26 2021 - 03:52:34 UTC

Original text of this message