Hi Tobias,
On Thu, 18 Feb 2021 at 23:02, Tobias Geerinckx-Rice via Bug reports for GNU
Guix 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 s
Sharlatan Hellseher 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 fi
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
Sharlatan Hellseher 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
./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
--
… наш разум - превосходная объяснительная
