From: Dariqq <dariqq@posteo.net>
To: 73587@debbugs.gnu.org
Subject: bug#73587: llvm@0.15 build failure on i686-linux
Date: Tue, 1 Oct 2024 19:22:10 +0000 [thread overview]
Message-ID: <c47b1809-d21d-437e-b7e1-f898323e4ede@posteo.net> (raw)
Hi,
After core-updates the llvm@0.15 pacakge is ooming during
'make-dynamic-linker-cache phase on i686-linux.
Was looking through the llvm.scm and this phase already gets skipped on
llvm@16, llvm@17 and llvm@18
From https://ci.guix.gnu.org/build/5769504/details
starting phase `make-dynamic-linker-cache'
GC Warning: Repeated allocation of very large block (appr. size 32772 KiB):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 65540 KiB):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 131076 KiB):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 262148 KiB):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 32772 KiB):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 65540 KiB):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 262148 KiB):
May lead to memory leak and poor performance
GC Warning: Failed to expand heap by 278532 KiB
GC Warning: Failed to expand heap by 262148 KiB
GC Warning: Out of Memory! Heap size: 3449 MiB. Returning NULL!
Warning: Unwind-only out of memory exception; skipping pre-unwind handler.
Warning: Unwind-only out of memory exception; skipping pre-unwind handler.
Warning: Unwind-only out of memory exception; skipping pre-unwind handler.
build process 18 exited with status 256
next reply other threads:[~2024-10-01 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 19:22 Dariqq [this message]
2024-10-01 20:00 ` bug#73587: llvm@0.15 build failure on i686-linux Dariqq
2024-10-05 10:16 ` bug#73587: Duplicate of 59365 Dariqq
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c47b1809-d21d-437e-b7e1-f898323e4ede@posteo.net \
--to=dariqq@posteo.net \
--cc=73587@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).