From: Vagrant Cascadian <vagrant@debian.org>
To: 48131@debbugs.gnu.org
Subject: bug#48131: build failure: 1.3.0rc1 on Debian i386 with guile-2.2
Date: Sat, 01 May 2021 19:17:12 -0700 [thread overview]
Message-ID: <87h7jlvpzr.fsf@yucca> (raw)
In-Reply-To: <875z03wcco.fsf@yucca>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
On 2021-04-30, Vagrant Cascadian wrote:
> I've been unable to build version 1.3.0rc1 for i386 on Debian:
>
> [ 70%] GUILEC gnu/packages/direct-connect.go
> [ 70%] GUILEC gnu/packages/disk.go
> GC Warning: Failed to expand heap by 8388608 bytes
> GC Warning: Failed to expand heap by 8388608 bytes
> ...
> GC Warning: Failed to expand heap by 8388608 bytes
> GC Warning: Failed to expand heap by 8388608 bytes
> Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS
> make[3]: *** [Makefile:6871: make-go] Aborted
>
>
> Debian is still using guile-2.2, so I'm guessing this is not a
> particularly well tested codepath anymore...
But strangely enough, it built fine on debian's build machines on all
supported architectures:
https://buildd.debian.org/status/package.php?p=guix&suite=experimental
*shrug*
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2021-05-02 2:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 0:01 bug#48131: build failure: 1.3.0rc1 on Debian i386 with guile-2.2 Vagrant Cascadian
2021-05-02 2:17 ` Vagrant Cascadian [this message]
2021-05-02 21:59 ` Ludovic Courtès
2021-05-02 22:17 ` Vagrant Cascadian
2021-05-02 22:50 ` Vagrant Cascadian
2021-05-03 19:54 ` Ludovic Courtès
2022-03-18 2:31 ` Maxim Cournoyer
2022-03-18 6:09 ` Vagrant Cascadian
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=87h7jlvpzr.fsf@yucca \
--to=vagrant@debian.org \
--cc=48131@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).