Re: [gentoo-user] cannot emerge chromium 89.0.4343.0

2020-12-10 Thread John Covici
On Wed, 09 Dec 2020 13:58:01 -0500, David Haller wrote: > > Hello, > > On Wed, 09 Dec 2020, John Covici wrote: > >On Wed, 09 Dec 2020 11:20:06 -0500, Mark Knecht wrote: > [..] > >FAILED: obj/v8/v8_base_without_compiler/intl-objects.o > [..] -O2 -pipe -c

Re: [gentoo-user] cannot emerge chromium 89.0.4343.0

2020-12-09 Thread David Haller
Hello, On Wed, 09 Dec 2020, John Covici wrote: >On Wed, 09 Dec 2020 11:20:06 -0500, Mark Knecht wrote: [..] >FAILED: obj/v8/v8_base_without_compiler/intl-objects.o [..] -O2 -pipe -c ../../v8/src/objects/intl-objects.cc -o obj/v8/v8_base_without_compiler/intl-objects.o

Re: [gentoo-user] cannot emerge chromium 89.0.4343.0

2020-12-09 Thread Matt Connell (Gmail)
On Wed, 2020-12-09 at 12:58 -0500, John Covici wrote: > is there something I should change? The system-icu use flag is set by default. You may want to unset it and try again: "www-client/chromium -system-icu" in a package.use file. As Michael suggested, performing a @world update first couldn't

Re: [gentoo-user] cannot emerge chromium 89.0.4343.0

2020-12-09 Thread John Covici
On Wed, 09 Dec 2020 12:39:16 -0500, Michael wrote: > > [1 ] > 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 ] > > > > > > On Wed, Dec 9, 2020 at 8:16 AM John Covici wrote: > > > > Hi. In my latest

Re: [gentoo-user] cannot emerge chromium 89.0.4343.0

2020-12-09 Thread Michael
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 ] > > > > On Wed, Dec 9, 2020 at 8:16 AM John Covici wrote: > > > Hi. In my latest update I cannot emerge Chromium 89.0.4343.0. I am > > > finding it very hard to

Re: [gentoo-user] cannot emerge chromium 89.0.4343.0

2020-12-09 Thread Mark Knecht
On Wed, Dec 9, 2020 at 8:16 AM John Covici 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