From: Zev Weiss <zweiss@equinix.com>
To: "Ananth, Rajesh" <rajesh.ananth@smartm.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: bitbake compilation errors
Date: Thu, 6 Jun 2024 23:14:41 +0000 [thread overview]
Message-ID: <20240606231440.GC6918@packtop> (raw)
In-Reply-To: <BN8PR04MB5906280BF43CA24D2EA9E1D094FA2@BN8PR04MB5906.namprd04.prod.outlook.com>
On Thu, Jun 06, 2024 at 12:57:31PM PDT, Ananth, Rajesh wrote:
>Bitbake, while compiling the nodejs-native keeps on failing. It happens irrespective of what platform I am building for. Does it require any package fixes for nodejs?
>
>Build environment: Linux bld-ub20s-openbmc 5.4.0-182-generic #202-Ubuntu SMP Fri Apr 26 12:29:36 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
>
>
>| g++ -o Release/obj.target/v8_turboshaft/deps/v8/src/compiler/turboshaft/memory-optimization-reducer.o ../deps/v8/src/compiler/turboshaft/memory-optimization-reducer.cc '-D_GLIBCXX_USE_CXX11_ABI=1' '-DNODE_OPENSSL_CONF_NAME=nodejs_conf' '-DICU_NO_USER_DATA_OVERRIDE' '-DV8_GYP_BUILD' '-DV8_TYPED_ARRAY_MAX_SIZE_IN_HEAP=64' '-D__STDC_FORMAT_MACROS' '-DV8_TARGET_ARCH_X64' '-DV8_HAVE_TARGET_OS' '-DV8_TARGET_OS_LINUX' '-DV8_EMBEDDER_STRING="-node.17"' '-DENABLE_DISASSEMBLER' '-DV8_PROMISE_INTERNAL_FIELD_COUNT=1' '-DV8_ENABLE_PRIVATE_MAPPING_FORK_OPTIMIZATION' '-DV8_SHORT_BUILTIN_CALLS' '-DOBJECT_PRINT' '-DV8_INTL_SUPPORT' '-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_USE_ZLIB' '-DV8_ENABLE_TURBOFAN' '-DV8_ENABLE_WEBASSEMBLY' '-DV8_ENABLE_JAVASCRIPT_PROMISE_HOOKS' '-DV8_ALLOCATION_FOLDING' '-DV8_ALLOCATION_SITE_TRACKING' '-DV8_ADVANCED_BIGINT_ALGORITHMS' -I/home/rajesh/openbmc/build/s7106/tmp/work/x86_64-linux/nodejs-native/20.11.1/recipe-sysroot-native/usr/include -I../deps/v8 -I../deps/v8/include -I.//Release/obj/gen/generate-bytecode-output-root -I.//Release/obj/gen -pthread -Wno-unused-parameter -Wno-return-type -fno-strict-aliasing -m64 -m64 -O3 -fno-omit-frame-pointer -fdata-sections -ffunction-sections -O3 -fno-rtti -fno-exceptions -std=gnu++17 -MMD -MF .//Release/.deps/Release/obj.target/v8_turboshaft/deps/v8/src/compiler/turboshaft/memory-optimization-reducer.o.d.raw -isystem/home/rajesh/openbmc/build/s7106/tmp/work/x86_64-linux/nodejs-native/20.11.1/recipe-sysroot-native/usr/include -isystem/home/rajesh/openbmc/build/s7106/tmp/work/x86_64-linux/nodejs-native/20.11.1/recipe-sysroot-native/usr/include -O2 -pipe -c
>| g++: fatal error: Killed signal terminated program cc1plus
I'd bet the odds are good this was caused by an OOM (out-of-memory)
condition on your build host -- if you have administrative access, check
dmesg or /var/log/kern.log to confirm. You might need a larger machine
to use for building OpenBMC, or possibly to serialize things if there
were other memory-hungry things running on it at the same time.
Zev
next prev parent reply other threads:[~2024-06-06 23:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 19:57 bitbake compilation errors Ananth, Rajesh
2024-06-06 23:14 ` Zev Weiss [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-15 11:23 BitBake Compilation errors Vamsi
2007-08-15 11:48 ` Dr. Michael Lauer
2007-08-15 4:10 Vamsi
2007-08-14 14:40 Vamsi
2007-08-14 16:13 ` Jim Sheldon
2007-08-15 9:53 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240606231440.GC6918@packtop \
--to=zweiss@equinix.com \
--cc=openbmc@lists.ozlabs.org \
--cc=rajesh.ananth@smartm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.