Re: www/chromium 148.0.7778.96 compile failure on 14.3-RELEASE-p11

On 5/11/26 06:57, George Mitchell wrote:
> On 5/10/26 10:56, George Mitchell wrote:
>> On 5/9/26 21:01, Mark Millard wrote:
>>> On 5/9/26 16:40, Bugs Beastie wrote:
>>>> May 9, 2026 22:35:11 Mark Millard <[email protected]>:
>>>>
>>>>> On 5/9/26 12:35, Mark Millard wrote:
>>>>>> On 5/9/26 08:00, Bugs Beastie wrote:
>>>>>>> May 9, 2026 14:52:53 George Mitchell <[email protected]>:
>>>>>>> [...]
>>
>> Limiting the number of jobs to two has fixed the problem, but (surprise)
>> the compile still hasn't finished.
>>
>> Other factor that changed this time: portmaster decided to upgrade to
>> llvm22.  Presumably I had previously been using llvm21.  (I also still
>> have installed on my machine llvm14,15,17,19.)  I'm tempted to go back
>> to llvm21.  Do others have experience with llvm22?           -- George
> 
> llvm22 limited to two jobs successfully completed the compile of the
> cited version of chromium at 2:32am this morning; i.e. over 30 hours
> from when I started.  I am going to try reverting to llvm21 and see if
> I can get a compile without limiting MAKE_JOBS_NUMBER.       -- George

Do you always use a devel/llvm* ? Or is your llvm21 use just a system
compiler toolchain? (devel/llvm* builds are likely notably bigger than
the system compiler toolchain related builds.)

Long term, at some point llvm21 will no long work. So it may be worth
some exploring how to cut the time over the time until then. (Not a
suggestion to use llvm22 anyway now.)

Another time frame issue is the builds of main's world are by default
debug builds and when such are installed and used, there is a sizable
scale factor on how long builds done in that environment take --even if
when kernel is a non-debug build.

-- 
===
Mark Millard
marklmi at yahoo.com