[gentoo-user] chromium build failure

[gentoo-user] chromium build failure

[allan gottlieb]

I ran the build failed twice, each time with MAKEOPTS="--jobs=1" and the
build logs are essentially identical.  After about 12 hours compiling and
36MB of build.log, the error shown below occurs

I have two laptops with *very* similar gentoo distributions.  The newer
machine had a successful build first try.  The second older (4 years)
machine had both failures.  Each machine has profile
default/linux/amd64/17.0/desktop/gnome/systemd

Thanks in advance for any help.

allan

================================================================

[132/15175] python ../../chrome/browser/resources/optimize_webui.py --host history --input ../../chrome/browser/resources/md_history --out_folder gen/chrome/browser/resources/md_history --depfile gen/chrome/browser/resources/md_history/build.d --html_in_files app.html lazy_load.html --html_out_files app.vulcanized.html lazy_load.vulcanized.html --js_out_files app.crisper.js lazy_load.crisper.js --exclude chrome://resources/html/util.html chrome://history/constants.html
FAILED: gen/chrome/browser/resources/md_history/app.vulcanized.html gen/chrome/browser/resources/md_history/lazy_load.vulcanized.html gen/chrome/browser/resources/md_history/app.crisper.js gen/chrome/browser/resources/md_history/lazy_load.crisper.js 
python ../../chrome/browser/resources/optimize_webui.py --host history --input ../../chrome/browser/resources/md_history --out_folder gen/chrome/browser/resources/md_history --depfile gen/chrome/browser/resources/md_history/build.d --html_in_files app.html lazy_load.html --html_out_files app.vulcanized.html lazy_load.vulcanized.html --js_out_files app.crisper.js lazy_load.crisper.js --exclude chrome://resources/html/util.html chrome://history/constants.html
../../third_party/node/linux/node-linux-x64/bin/node ../../third_party/node/node_modules/polymer-bundler/lib/bin/polymer-bundler --exclude chrome://resources/html/polymer.html --exclude chrome://resources/polymer/v1_0/polymer/polymer.html --exclude chrome://resources/polymer/v1_0/polymer/polymer-micro.html --exclude chrome://resources/polymer/v1_0/polymer/polymer-mini.html --exclude chrome://resources/polymer/v1_0/web-animations-js/web-animations-next-lite.min.js --exclude chrome://resources/css/roboto.css --exclude chrome://resources/css/text_defaults.css --exclude chrome://resources/css/text_defaults_md.css --exclude chrome://resources/js/load_time_data.js --inline-css --inline-scripts --rewrite-urls-in-templates --strip-comments --redirect "chrome://resources/cr_components/|../../ui/webui/resources/cr_components" --redirect "chrome://resources/cr_elements/|../../ui/webui/resources/cr_elements" --redirect "chrome://resources/css/|../../ui/webui/resources/css" --redirect "chrome://resources/html/|../../ui/webui/resources/html" --redirect "chrome://resources/js/|../../ui/webui/resources/js" --redirect "chrome://resources/polymer/v1_0/|../../third_party/polymer/v1_0/components-chromium" --exclude chrome://resources/html/util.html --exclude chrome://history/constants.html --exclude strings.js --exclude chrome://history/strings.js --manifest-out /var/tmp/portage/www-client/chromium-63.0.3239.132/work/chromium-63.0.3239.132/out/Release/gen/chrome/browser/resources/md_history/history_requestlist.txt --root /var/tmp/portage/www-client/chromium-63.0.3239.132/work/chromium-63.0.3239.132/chrome/browser/resources/md_history --redirect "chrome://history/|/var/tmp/portage/www-client/chromium-63.0.3239.132/work/chromium-63.0.3239.132/chrome/browser/resources/md_history" --out-dir gen/chrome/browser/resources/md_history/bundled --shell app.html --in-html app.html --in-html lazy_load.html failed: module.js:471
    throw err;
    ^

Error: Cannot find module '/var/tmp/portage/www-client/chromium-63.0.3239.132/work/chromium-63.0.3239.132/third_party/node/node_modules/polymer-bundler/lib/bin/polymer-bundler'
    at Function.Module._resolveFilename (module.js:469:15)
    at Function.Module._load (module.js:417:25)
    at Module.runMain (module.js:604:10)
    at run (bootstrap_node.js:383:7)
    at startup (bootstrap_node.js:149:9)
    at bootstrap_node.js:496:3

Traceback (most recent call last):
  File "../../chrome/browser/resources/optimize_webui.py", line 252, in <module>
    main(sys.argv[1:])
  File "../../chrome/browser/resources/optimize_webui.py", line 235, in main
    manifest_out_path = _optimize(args.input, args)
  File "../../chrome/browser/resources/optimize_webui.py", line 159, in _optimize
    ] + in_html_args)
  File "../../third_party/node/node.py", line 28, in RunNode
    raise
TypeError: exceptions must be old-style classes or derived from BaseException, not NoneType
ninja: build stopped: subcommand failed.
 [31;01m*[0m ERROR: www-client/chromium-63.0.3239.132::gentoo failed (compile phase):
 [31;01m*[0m   ninja -v -j1 -l0 -C out/Release chrome chromedriver failed
 [31;01m*[0m 
 [31;01m*[0m Call stack:
 [31;01m*[0m     ebuild.sh, line  124:  Called src_compile
 [31;01m*[0m   environment, line 5079:  Called eninja '-C' 'out/Release' 'chrome' 'chromedriver'
 [31;01m*[0m   environment, line 1748:  Called die
 [31;01m*[0m The specific snippet of code:
 [31;01m*[0m       "$@" || die "${nonfatal_args[@]}" "${*} failed"
 [31;01m*[0m 
 [31;01m*[0m If you need support, post the output of `emerge --info '=www-client/chromium-63.0.3239.132::gentoo'`,
 [31;01m*[0m the complete build log and the output of `emerge -pqv '=www-client/chromium-63.0.3239.132::gentoo'`.
 [32;01m*[0m 
 [32;01m*[0m MemTotal:        8045252 kB
 [32;01m*[0m SwapTotal:       2097148 kB
 [32;01m*[0m 
 [31;01m*[0m The complete build log is located at '/var/tmp/portage/www-client/chromium-63.0.3239.132/temp/build.log'.
 [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/www-client/chromium-63.0.3239.132/temp/environment'.
 [31;01m*[0m Working directory: '/var/tmp/portage/www-client/chromium-63.0.3239.132/work/chromium-63.0.3239.132'
 [31;01m*[0m S: '/var/tmp/portage/www-client/chromium-63.0.3239.132/work/chromium-63.0.3239.132'

Re: [gentoo-user] chromium build failure

[Canek Peláez Valdés]

[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]

On Wed, Jan 24, 2018 at 10:11 PM, allan gottlieb <gottlieb@nyu.edu> wrote:
>
> I ran the build failed twice, each time with MAKEOPTS="--jobs=1" and the
> build logs are essentially identical.  After about 12 hours compiling and
> 36MB of build.log, the error shown below occurs
>
> I have two laptops with *very* similar gentoo distributions.  The newer
> machine had a successful build first try.  The second older (4 years)
> machine had both failures.  Each machine has profile
> default/linux/amd64/17.0/desktop/gnome/systemd

If the USE flags for chromium on both machines are the same, simply create
a binary package from the machine that already built it.

machine1:

$ quickpkg --include-config=y www-client/chromium

machine2

$ sync --delete -Pvase ssh machine1:/usr/portage/packages/
/usr/portage/packages/
$ emerge --nodeps -1Kv www-client/chromium

I have two powerful desktop computers (home and office) and a laptop. Their
USE flags are identical; I just compile in one of them and generate binary
packages for the other two. It helps (but it's not 100% required) if the
/usr/portage tree is identical (I sync only with one and rsync the others,
followed by emerge --metadata).

Regards.
--
Dr. Canek Peláez Valdés
Profesor de Carrera Asociado C
Departamento de Matemáticas
Facultad de Ciencias
Universidad Nacional Autónoma de México

[-- Attachment #2: Type: text/html, Size: 1675 bytes --]

Re: [gentoo-user] chromium build failure

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 618 bytes --]

On Wed, 24 Jan 2018 22:29:59 -0600, Canek Peláez Valdés wrote:

> > I have two laptops with *very* similar gentoo distributions.  The
> > newer machine had a successful build first try.  The second older (4
> > years) machine had both failures.  Each machine has profile
> > default/linux/amd64/17.0/desktop/gnome/systemd  
> 
> If the USE flags for chromium on both machines are the same, simply
> create a binary package from the machine that already built it.

Good idea, as long as the CFLAGS are the same too.


-- 
Neil Bothwick

Like an atheist in a grave: all dressed up and no place to go.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] chromium build failure

[allan gottlieb]

On Thu, Jan 25 2018, Neil Bothwick wrote:

> On Wed, 24 Jan 2018 22:29:59 -0600, Canek Peláez Valdés wrote:
>
>> > I have two laptops with *very* similar gentoo distributions.  The
>> > newer machine had a successful build first try.  The second older (4
>> > years) machine had both failures.  Each machine has profile
>> > default/linux/amd64/17.0/desktop/gnome/systemd  
>> 
>> If the USE flags for chromium on both machines are the same, simply
>> create a binary package from the machine that already built it.
>
> Good idea, as long as the CFLAGS are the same too.

Thank you both.  I will try it.
allan

Re: [gentoo-user] chromium build failure

[allan gottlieb]

On Wed, Jan 24 2018, Canek Peláez Valdés wrote:

> On Wed, Jan 24, 2018 at 10:11 PM, allan gottlieb <gottlieb@nyu.edu> wrote:
>>
>> I ran the build failed twice, each time with MAKEOPTS="--jobs=1" and the
>> build logs are essentially identical.  After about 12 hours compiling and
>> 36MB of build.log, the error shown below occurs
>>
>> I have two laptops with *very* similar gentoo distributions.  The newer
>> machine had a successful build first try.  The second older (4 years)
>> machine had both failures.  Each machine has profile
>> default/linux/amd64/17.0/desktop/gnome/systemd
>
> If the USE flags for chromium on both machines are the same, simply create
> a binary package from the machine that already built it.
>
> machine1:
>
> $ quickpkg --include-config=y www-client/chromium
>
> machine2
>
> $ sync --delete -Pvase ssh machine1:/usr/portage/packages/
> /usr/portage/packages/
> $ emerge --nodeps -1Kv www-client/chromium

Canek,

Again thank you for your recipe.

I have two questions, one trivial, one hopefully easy.

1. (trivial) In your recipe did you mean "rsync", not "sync"?

2. I have a number of quickpkgs built.  Is it needed that
   they all be updated and some removed or can I just do
   the following command

   rsync -Pvase ssh machine1:/var/portage/packages/www-client \
                             /var/portage/packages

   Notes: I use /var not /usr for portage
          machine2 has no dir /var/portage/packages/www-client

Thanks in advance,
allan

Re: [gentoo-user] chromium build failure

[Canek Peláez Valdés]

[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]

On Wed, Jan 31, 2018 at 1:29 PM, allan gottlieb <gottlieb@nyu.edu> wrote:
[snip]
> I have two questions, one trivial, one hopefully easy.
>
> 1. (trivial) In your recipe did you mean "rsync", not "sync"?

I sync ("emerge --sync") only one machine, and then I rsync from there to
my other computers. After the rsync is done, you need to do "emerge
--metadata" in the recipient machine (--sync does that for you
automatically).

> 2. I have a number of quickpkgs built.  Is it needed that
>    they all be updated and some removed or can I just do
>    the following command
>
>    rsync -Pvase ssh machine1:/var/portage/packages/www-client \
>                              /var/portage/packages
>
>    Notes: I use /var not /usr for portage
>           machine2 has no dir /var/portage/packages/www-client

I honestly don't know. There is a /usr/portage/packages/Packages with a lot
of meta information, and I'm not 100% sure whether is absolutely required.
Then again, creating binary packages is so fast that I usually delete
/usr/portage/packages after updating my non-compiling machines. I know of
people who maintain a large repository of binary packages (they can be
built automatically with FEATURES="buildpkg" in make.conf), but I just
create them when needed.

Regards.
--
Dr. Canek Peláez Valdés
Profesor de Carrera Asociado C
Departamento de Matemáticas
Facultad de Ciencias
Universidad Nacional Autónoma de México

[-- Attachment #2: Type: text/html, Size: 1708 bytes --]

Re: [gentoo-user] chromium build failure

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 592 bytes --]

On Wed, 31 Jan 2018 15:38:27 -0600, Canek Peláez Valdés wrote:

> I sync ("emerge --sync") only one machine, and then I rsync from there
> to my other computers. After the rsync is done, you need to do "emerge
> --metadata" in the recipient machine (--sync does that for you
> automatically).

If you run the rsync daemon on the machine you --sync, you can set that
as the source for the other computers and emerge --sync on them, which
saves the extra step of updating the metadata.


-- 
Neil Bothwick

Men who go out with flat chested woman have reasons for feeling down

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] chromium build failure

[allan gottlieb]

On Wed, Jan 31 2018, Canek Peláez Valdés wrote:

> On Wed, Jan 31, 2018 at 1:29 PM, allan gottlieb <gottlieb@nyu.edu> wrote:
> [snip]
>> I have two questions, one trivial, one hopefully easy.
>>
>> 1. (trivial) In your recipe did you mean "rsync", not "sync"?
>
> I sync ("emerge --sync") only one machine, and then I rsync from there to
> my other computers. After the rsync is done, you need to do "emerge
> --metadata" in the recipient machine (--sync does that for you
> automatically).

So sync referred to an emerge command and when you copied files from
machine to machine you used rsync.  Thanks.
>
>> 2. I have a number of quickpkgs built.  Is it needed that
>>    they all be updated and some removed or can I just do
>>    the following command
>>
>>    rsync -Pvase ssh machine1:/var/portage/packages/www-client \
>>                              /var/portage/packages
>>
>>    Notes: I use /var not /usr for portage
>>           machine2 has no dir /var/portage/packages/www-client
>
> I honestly don't know. There is a /usr/portage/packages/Packages with a lot
> of meta information, and I'm not 100% sure whether is absolutely required.
> Then again, creating binary packages is so fast that I usually delete
> /usr/portage/packages after updating my non-compiling machines. I know of
> people who maintain a large repository of binary packages (they can be
> built automatically with FEATURES="buildpkg" in make.conf), but I just
> create them when needed.

I have FEATURES="buildsyspkg" on all machines for safety.
It has worked in the sense that I have never needed to use
the resulting packages.

But I see your point that /var/portage/packages/Packages
may need to be updated on the target machine so it is probably
best to do your rsync of all of /var/portage/packages
>
> Regards.
> --
> Dr. Canek Peláez Valdés

thanks,
allan