From: Guillaume Le Vaillant <glv@posteo.net>
To: Sharlatan Hellseher <sharlatanus@gmail.com>
Cc: 46624-done@debbugs.gnu.org
Subject: bug#46624: Too many heap sections: Increase MAXHINCR or MAX_HEAP_SEC
Date: Fri, 19 Feb 2021 09:19:43 +0100 [thread overview]
Message-ID: <87blcg8o68.fsf@yamatai> (raw)
In-Reply-To: <CAO+9K5qWmYm7NArHKQjgPAOPAtm535jM6qT4JBhT-rVO_ZHkdA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
Sharlatan Hellseher <sharlatanus@gmail.com> skribis:
> Hi,
>
> Yes it looks like issue on my end only.
> I've doped my local branch pull upstream and I could rebuild it now.
> Issue could be closed.
>
> Thanks
>
> hellseher@guix-base-20210210 ~/code/guix [env]$ ./pre-inst-env guix
> build sbcl-cffi
> ;;; note: source file /home/hellseher/code/guix/gnu/packages/lisp-xyz.scm
> ;;; newer than compiled /home/hellseher/code/guix/gnu/packages/lisp-xyz.go
> ;;; note: source file /home/hellseher/code/guix/gnu/packages/emacs-xyz.scm
> ;;; newer than compiled
> /home/hellseher/code/guix/gnu/packages/emacs-xyz.go
> ;;; note: source file /home/hellseher/code/guix/gnu/packages/games.scm
> ;;; newer than compiled /home/hellseher/code/guix/gnu/packages/games.go
> ;;; note: source file /home/hellseher/code/guix/gnu/packages/telegram.scm
> ;;; newer than compiled /home/hellseher/code/guix/gnu/packages/telegram.go
> /gnu/store/x9ainb8phlprackcdwl1a8w0xh1bh18g-sbcl-cffi-0.23.0
Ok, closing.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
prev parent reply other threads:[~2021-02-19 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 20:42 bug#46624: Too many heap sections: Increase MAXHINCR or MAX_HEAP_SEC Sharlatan Hellseher
2021-02-18 21:05 ` Guillaume Le Vaillant
2021-02-18 22:02 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-02-24 22:41 ` zimoun
[not found] ` <CAO+9K5qWmYm7NArHKQjgPAOPAtm535jM6qT4JBhT-rVO_ZHkdA@mail.gmail.com>
2021-02-19 8:19 ` Guillaume Le Vaillant [this message]
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=87blcg8o68.fsf@yamatai \
--to=glv@posteo.net \
--cc=46624-done@debbugs.gnu.org \
--cc=sharlatanus@gmail.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.
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).