./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 Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECS Aborted -- … наш разум - превосходная объяснительная машина которая способна найти смысл почти в чем угодно, истолковать любой феномен, но совершенно не в состоянии принять мысль о непредсказуемости.
[-- Attachment #1: Type: text/plain, Size: 618 bytes --] Sharlatan Hellseher <sharlatanus@gmail.com> skribis: > ./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 Too many > heap sections: Increase MAXHINCR or MAX_HEAP_SECS > Aborted With Guix at 5fccdbc079402eee345684bcbd1b1d0306cab1e8 I don't reproduce this issue. From the warning and error messages you get, it looks like you changed something in 'lisp-xyz.scm' and Guix fails to compile it. Is it the case? If yes, there is probably a bug in the changes you made. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 247 bytes --]
[-- Attachment #1: Type: text/plain, Size: 465 bytes --] Guillaume Le Vaillant 写道: > From the warning and error messages you get, it looks like you > changed > something in 'lisp-xyz.scm' and Guix fails to compile it. > Is it the case? If yes, there is probably a bug in the changes > you made. More specifically, it's likely an input cycle (infinite loop of A needs B needs ... needs A). Guix doesn't [yet] detect these, and takes them literally until memory is exhausted. Kind regards, T G-R [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 247 bytes --]
[-- 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 --]
Hi Tobias,
On Thu, 18 Feb 2021 at 23:02, Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:
> More specifically, it's likely an input cycle (infinite loop of A
> needs B needs ... needs A). Guix doesn't [yet] detect these, and
> takes them literally until memory is exhausted.
Where should this feature go? Under “guix lint” via another checker or
“guix build” walking the graph to detect cycles before really building?
Cheers,
simon