On Wed, 09 Dec 2020 12:39:16 -0500,
Michael wrote:
>
> [1 <text/plain; UTF-8 (7bit)>]
> On Wednesday, 9 December 2020 17:31:29 GMT John Covici wrote:
> > On Wed, 09 Dec 2020 11:20:06 -0500,
> >
> > Mark Knecht wrote:
> > > [1 <text/plain; UTF-8 (7bit)>]
> > >
> > > On Wed, Dec 9, 2020 at 8:16 AM John Covici <cov...@ccs.covici.com> wrote:
> > > > Hi. In my latest update I cannot emerge Chromium 89.0.4343.0. I am
> > > > finding it very hard to tell even where the error is, so I am asking
> > > > for help to figure this out. I am attaching the entire build log to
> > > > this message because someone smarter than myself may be able to tell
> > > > me what is happpening here.
> > > >
> > > > Thanks in advance for any suggestions.
> > > >
> > > > --
> > > > Your life is like a penny. You're going to lose it. The question is:
> > > > How do
> > > > you spend it?
> > > >
> > > > John Covici wb2una
> > > > cov...@ccs.covici.com
> > >
> > > Down near the bottom it says (something like - I cannot copy it for some
> > > reason) v8_base_without_compiler/intl-objects failed.
> > >
> > > It seems V8 is Google's Javascript stuff.
> > >
> > > Building with -j1 would likely fail exactly where the problem is. I think
> > > it's building with -j2 which means this error is 1 back.
> > >
> > > No idea how to solve.
> >
> > OK, here it is with -j1, still not sure where the exact error is:
>
> I think it complains about the internationalisation components for unicode -
> are you building it with USE="+system-icu"? Perhaps without it the bundled
> code will work better. Or, run a @world update first and then come back to
> it
> in case everything falls in line and completes without an error.
the only chromium related use flag I have is
>=net-libs/nodejs-13.7.0-r1 inspector
Otherwise I am using the defaults -- is there something I should
change?
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici wb2una
cov...@ccs.covici.com
