inja: build stopped: subcommand failed.

• ERROR: www-client/chromium-91.0.4472.77::browser-kit failed (compile phase):
• ninja -v -j8 -l0 -C out/Release v8_context_snapshot_generator failed
  *
• Call stack:
• ebuild.sh, line 93: Called src_compile
• environment, line 4369: Called eninja '-C' 'out/Release' 'v8_context_snapshot_generator'
• environment, line 2026: Called die
• The specific snippet of code:
• "$@" || die "${nonfatal_args[@]}" "${*} failed"
  *
• If you need support, post the output of `emerge --info '=www-client/chromium-91.0.4472.77::browser-kit'`,
• the complete build log and the output of `emerge -pqv '=www-client/chromium-91.0.4472.77::browser-kit'`.
  *
• MemTotal: 7961208 kB
• SwapTotal: 8388604 kB
  *
• The complete build log is located at '/var/tmp/portage/www-client/chromium-91.0.4472.77/temp/build.log'.
• The ebuild environment file is located at '/var/tmp/portage/www-client/chromium-91.0.4472.77/temp/environment'.
• Working directory: '/var/tmp/portage/www-client/chromium-91.0.4472.77/work/chromium-91.0.4472.77'
• S: '/var/tmp/portage/www-client/chromium-91.0.4472.77/work/chromium-91.0.4472.77'

• CONFIG_COMPAT_VDSO causes segfaults (bug #556286)
• Please check to make sure these options are set correctly.
• Failure to do so may cause unexpected problems.
• Adding experimental glibc-2.33 sandbox patch. Seccomp sandbox might
• still not work correctly. In case of issues, try to disable seccomp
• sandbox by adding --disable-seccomp-filter-sandbox to CHROMIUM_FLAGS
• in /etc/chromium/default.
• ERROR: www-client/chromium-91.0.4472.77::browser-kit failed (compile phase):
• ninja -v -j8 -l0 -C out/Release v8_context_snapshot_generator failed
  *
• Call stack:
• ebuild.sh, line 93: Called src_compile
• environment, line 4369: Called eninja '-C' 'out/Release' 'v8_context_snapshot_generator'
• environment, line 2026: Called die
• The specific snippet of code:
• "$@" || die "${nonfatal_args[@]}" "${*} failed"
  *