Re: build of www/chromium stops in node18
- In reply to: bob prohaska : "build of www/chromium stops in node18"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 11 Jul 2023 02:25:21 UTC
On Jul 10, 2023, at 19:04, bob prohaska <fbsd@www.zefox.net> wrote: > While compiling www/chromium on an 8GB Pi4 poudriere seems to have > trouble compiling www/node. > > The error message is: > > ^ > c++ -o /wrkdirs/usr/ports/www/node18/work/node-v18.16.1/out/Release/obj.target/v8_compiler/deps/v8/src/compiler/backend/instruction-schedu > ler.o ../deps/v8/src/compiler/backend/instruction-scheduler.cc '-D_GLIBCXX_USE_CXX11_ABI=1' '-DNODE_OPENSSL_CONF_NAME=nodejs_conf' '-DNODE_O > PENSSL_CERT_STORE' '-DICU_NO_USER_DATA_OVERRIDE' '-DV8_GYP_BUILD' '-DV8_TYPED_ARRAY_MAX_SIZE_IN_HEAP=64' '-D__STDC_FORMAT_MACROS' '-DV8_TARG > ET_ARCH_ARM64' '-DV8_EMBEDDER_STRING="-node.26"' '-DENABLE_DISASSEMBLER' '-DV8_PROMISE_INTERNAL_FIELD_COUNT=1' '-DOBJECT_PRINT' '-DV8_INTL_S > UPPORT' '-DV8_ATOMIC_OBJECT_FIELD_WRITES' '-DV8_ENABLE_LAZY_SOURCE_POSITIONS' '-DV8_USE_SIPHASH' '-DV8_SHARED_RO_HEAP' '-DV8_WIN64_UNWINDING_INFO' '-DV8_ENABLE_REGEXP_INTERPRETER_THREADED_DISPATCH' '-DV8_ENABLE_WEBASSEMBLY' '-DV8_ENABLE_JAVASCRIPT_PROMISE_HOOKS' '-DV8_ALLOCATION_FOLDING' '-DV8_ALLOCATION_SITE_TRACKING' '-DV8_SCRIPTORMODULE_LEGACY_LIFETIME' '-DV8_ADVANCED_BIGINT_ALGORITHMS' -I../deps/v8 -I../deps/v8/include -I/wrkdirs/usr/ports/www/node18/work/node-v18.16.1/out/Release/obj/gen/generate-bytecode-output-root -I/wrkdirs/usr/ports/www/node18/work/node-v18.16.1/out/Release/obj/gen -msign-return-address=all -pthread -Wno-unused-parameter -Wno-return-type -fno-strict-aliasing -O3 -fno-omit-frame-pointer -fdata-sections -ffunction-sections -O3 -fno-rtti -fno-exceptions -std=gnu++17 -MMD -MF /wrkdirs/usr/ports/www/node18/work/node-v18.16.1/out/Release/.deps//wrkdirs/usr/ports/www/node18/work/node-v18.16.1/out/Release/obj.target/v8_compiler/deps/v8/src/compiler/backend/instruction-scheduler.o.d.raw -isystem /usr/local/include -O2 -pipe -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -isystem /usr/local/include -c > 1 error generated. > gmake[2]: *** [tools/v8_gypfiles/v8_compiler.target.mk:257: /wrkdirs/usr/ports/www/node18/work/node-v18.16.1/out/Release/obj.target/v8_compiler/deps/v8/src/compiler/backend/frame-elider.o] Error 1 > gmake[2]: *** Waiting for unfinished jobs.... > In file included from ../deps/v8/src/compiler/backend/instruction-scheduler.cc:5: > In file included from ../deps/v8/src/compiler/backend/instruction-scheduler.h:10: > In file included from ../deps/v8/src/compiler/backend/instruction.h:13: > In file included from ../deps/v8/src/codegen/external-reference.h:9: > In file included from ../deps/v8/src/runtime/runtime.h:11: > ../deps/v8/src/base/bit-field.h:43:29: error: integer value 31 is outside the valid range of values [0, 15] for the enumeration type 'AddressingMode' [-Wenum-constexpr-conversion] > static constexpr T kMax = static_cast<T>(kNumValues - 1); > ^ > 1 error generated. > gmake[2]: *** [tools/v8_gypfiles/v8_compiler.target.mk:257: /wrkdirs/usr/ports/www/node18/work/node-v18.16.1/out/Release/obj.target/v8_compiler/deps/v8/src/compiler/backend/gap-resolver.o] Error 1 > 1 error generated. > gmake[2]: *** [tools/v8_gypfiles/v8_compiler.target.mk:257: /wrkdirs/usr/ports/www/node18/work/node-v18.16.1/out/Release/obj.target/v8_compiler/deps/v8/src/compiler/backend/instruction-scheduler.o] Error 1 > 1 error generated. > gmake[2]: *** [tools/v8_gypfiles/v8_compiler.target.mk:257: /wrkdirs/usr/ports/www/node18/work/node-v18.16.1/out/Release/obj.target/v8_compiler/deps/v8/src/compiler/backend/code-generator.o] Error 1 > rm 01fb7dc823dadb09180497a1d2208cb741153ab9.intermediate efbd25df71d68976ddbb5dffa7cf4e2eb8586cf8.intermediate e70cc67dd10544f6cee68730cfce06f3c676d44d.intermediate > gmake[1]: *** [Makefile:134: node] Error 2 > gmake[1]: Leaving directory '/wrkdirs/usr/ports/www/node18/work/node-v18.16.1' > ===> Compilation failed unexpectedly. > Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to > the maintainer. > *** Error code 1 > > Stop. > make: stopped in /usr/ports/www/node18 > > I've tried git reset --hard in /usr/ports, no change. > It's unclear if this is a housekeeping problem on my > end or something larger. www/chromium has built in the > past, so the machine is up to the task. > > The system is at > FreeBSD nemesis.zefox.com 14.0-CURRENT FreeBSD 14.0-CURRENT #73 main-2176c9ab71: > Sun Jul 2 19:24:19 PDT 2023 bob@nemesis.zefox.com:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 It is not just you: http://ampere2.nyi.freebsd.org/data/main-arm64-default/pa9d219203e83_se64780fbc3/logs/errors/node18-18.16.0.log shows the same type of failure on the FreeBSD build server. === Mark Millard marklmi at yahoo.com