From: "Livius" <egyszeregy@freemail.hu>
To: meta-freescale@lists.yoctoproject.org
Subject: u-boot-fslc 2022.10 failed with exit code '137' (using too much memory) #yocto #kirkstone #meta-freescale #u-boot
Date: Tue, 29 Nov 2022 01:32:58 -0800 [thread overview]
Message-ID: <DN5C.1669714378815913690.nKiW@lists.yoctoproject.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 479 bytes --]
New u-boot-fslc_2022.10.bb is failed always with exit code '137' which means the available memory has been exhausted, so 16 GB DDR4 RAM memory was not enough for this single recipe build on Ubuntu 20.04 desktop Linux.
https://www.containiq.com/post/exit-code-137
Similar problem was happened in mender forum: https://hub.mender.io/t/uboot-auto-configure-exit-code-137/3624
Please fix it, i think it is not normally that 16 GB RAM is not enough for a single recipe build.
[-- Attachment #2: Type: text/html, Size: 550 bytes --]
next reply other threads:[~2022-11-29 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 9:32 Livius [this message]
2022-11-29 11:34 ` [meta-freescale] u-boot-fslc 2022.10 failed with exit code '137' (using too much memory) #yocto #kirkstone #meta-freescale #u-boot Otavio Salvador
2022-11-29 13:47 ` u-boot-fslc 2022.10 failed with exit code '137' (using too much memory) #yocto #kirkstone #meta-freescale Livius
2022-11-29 14:45 ` [meta-freescale] " Bas Mevissen
2022-12-01 22:14 ` Livius
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=DN5C.1669714378815913690.nKiW@lists.yoctoproject.org \
--to=egyszeregy@freemail.hu \
--cc=meta-freescale@lists.yoctoproject.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).