Date: Fri, 16 Jul 2021 11:31:31 -0700 From: Mark Millard via freebsd-ports <freebsd-ports@freebsd.org> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-ports@freebsd.org Subject: Re: RPi4, www/chromium, FAILED: v8_context_snapshot_generator Message-ID: <8DE1F845-BF32-4D51-AD97-1361554B5160@yahoo.com> In-Reply-To: <C618910F-6B53-449A-92AC-47E0D429921D@yahoo.com> References: <C618910F-6B53-449A-92AC-47E0D429921D@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Jul-16, at 11:11, Mark Millard <marklmi at yahoo.com> wrote: > From: bob prohaska <fbsd_at_www.zefox.net> wrote on > Date: Fri, 16 Jul 2021 08:40:24 -0700 : >=20 >> While compiling www/chromium on an 8GB RPI4 poudriere stopped with >> FAILED: v8_context_snapshot_generator >>=20 >> Does anybody recognize this error? If it helps I can put the=20 >> machine on the net via http so folks can browse relevant parts >> of the filesystem. Ports were last updated July 12. >=20 >=20 > "v8_context_snapshot_generator" is not a FreeBSD message but a > program in chromium's source code, for example: >=20 > = https://chromium.googlesource.com/chromium/src/+/66.0.3359.181/tools/v8_co= ntext_snapshot/v8_context_snapshot_generator.cc >=20 > Its comments before in main (int argc, cha** argv) { . . . } are: >=20 > // This program takes a snapshot of V8 contexts and writes it out as a = file. > // The snapshot file is consumed by Blink. > // > // Usage: > // % v8_context_snapshot_generator --output_file=3D<filename> >=20 > My guess is that any actual error report but what happened to > v8_context_snapshot_generator is earlier and that "FAILED: > v8_context_snapshot_generator" is a later consequence of > earlier activity. >=20 > You may need to expose the log file. >=20 It may be that some or all relevant text is after that line, unlike my guess. I found on the web: FAILED: v8_context_snapshot_generator=20 ../../third_party/llvm-build/Release+Asserts/bin/clang++ = -Wl,--fatal-warnings -Wl,--build-id=3Dsha1 -fPIC -Wl,-z,noexecstack = -Wl,-z,relro -Wl,-z,now -Wl,-z,defs -Wl,--as-needed -fuse-ld=3Dlld = -Wl,--icf=3Dall -Wl,--color-diagnostics -flto=3Dthin=20 -Wl,--thinlto-jobs=3D8 -Wl,--thinlto-cache-dir=3Dthinlto-cache = -Wl,--thinlto-cache-policy,cache_size=3D10\%:cache_size_bytes=3D10g:cache_= size_files=3D100000 -Wl,--lto-O0 -fwhole-program-vtables -m64 -Werror = -Wl,-O2 -Wl,--gc-sections -Wl,--gdb-inde x -rdynamic -nostdlib++ = --sysroot=3D../../build/linux/debian_sid_amd64-sysroot = -L../../build/linux/debian_sid_amd64-sysroot/usr/local/lib/x86_64-linux-gn= u -L../../build/linux/debian_sid_amd64-sysroot/lib/x86_64-linux-gnu = -L../../build/linu x/debian_sid_amd64-sysroot/usr/lib/x86_64-linux-gnu -fsanitize=3Dcfi-vcall= -fsanitize=3Dcfi-icall -pie -Wl,--disable-new-dtags -Wl,--icf=3Dnone = -L../../build/linux/debian_sid_amd64-sysroot/usr/lib/x86_64-linux-gnu -o = "./v8_context_snapshot_gen erator" -Wl,--start-group @"./v8_context_snapshot_generator.rsp" = -Wl,--end-group -ldl -lpthread -lrt -lgmodule-2.0 -lglib-2.0 = -lgobject-2.0 -lgthread-2.0 -lnss3 -lnssutil3 -lsmime3 -lplds4 -lplc4 = -lnspr4 -lresolv -lgio-2.0 -lexpat -lu uid -lX11 -lX11-xcb -lxcb -lXcomposite -lXcursor -lXdamage -lXext = -lXfixes -lXi -lXrender -lXtst -lXrandr -lpci -lXss -ldbus-1 -lasound = -lm -lz=20 clang: error: unable to execute command: Killed clang: error: linker command failed due to signal (use -v to see = invocation) ninja: build stopped: subcommand failed. . . . (more not shown) . . . It seems to put related material after the line. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8DE1F845-BF32-4D51-AD97-1361554B5160>