From: Foo Chuan Wei <chuanwei.foo@hotmail.com>
To: brettg@gnu.org
Cc: 38606@debbugs.gnu.org
Subject: [bug#38606] [WIP v2 1/1] gnu: Add smlnj.
Date: Wed, 10 Nov 2021 11:07:38 +0000 [thread overview]
Message-ID: <PU1PR01MB2155FCFCE641861DAB6A21DE8D939@PU1PR01MB2155.apcprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <87lfq78n1a.fsf@gnu.org>
> One particularly interesting issue of this package is, after retrieving
> a viable BOOTLIST file to use for compilation, we are left with this.
>
> --8<---------------cut here---------------start------------->8---
> brettg@oryx ~/Repos/smlnj [env]$ ./bin/.run/run.amd64-linux
> ./bin/.run/run.amd64-linux: Fatal error -- no in-core heap image found
> --8<---------------cut here---------------end--------------->8---
>
> Not quite sure how to investigate this issue. If anybody has any
> insights please share, otherwise I will just contact upstream in a the
> coming days.
For future reference:
It seems that this error can be avoided by deleting "PATH=/bin:/usr/bin"
from runtime/config/gen-posix-names.sh. In any case, /bin and /usr/bin
do not exist in Guix's build environment.
next prev parent reply other threads:[~2021-11-10 11:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 4:04 [bug#38606] [WIP SMLnj 0/1] Add SMLnj Brett Gilio
2019-12-14 4:06 ` [bug#38606] [WIP SMLnj 1/1] gnu: Add smlnj Brett Gilio
2020-01-16 0:36 ` [bug#38606] [WIP v2 0/1] Add SMLNJ Brett Gilio
2020-01-16 0:36 ` [bug#38606] [WIP v2 1/1] gnu: Add smlnj Brett Gilio
2020-01-16 14:59 ` Brett Gilio
2021-10-29 23:33 ` [bug#38606] [WIP SMLnj 0/1] Add SMLnj Tim Lee
2021-11-10 11:07 ` Foo Chuan Wei [this message]
2021-11-07 15:00 ` Foo Chuan Wei
2021-11-08 21:40 ` Foo Chuan Wei
2021-11-09 10:03 ` Josselin Poiret via Guix-patches via
2021-11-10 9:21 ` Foo Chuan Wei
2021-12-12 16:37 ` bug#38606: " Chuan Wei Foo
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PU1PR01MB2155FCFCE641861DAB6A21DE8D939@PU1PR01MB2155.apcprd01.prod.exchangelabs.com \
--to=chuanwei.foo@hotmail.com \
--cc=38606@debbugs.gnu.org \
--cc=brettg@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.