From: Foo Chuan Wei <chuanwei.foo@hotmail.com>
To: philip@philipmcgrath.com
Cc: help-guix@gnu.org
Subject: Re: How to add /bin/sh to the build environment
Date: Tue, 9 Nov 2021 03:51:43 +0000 [thread overview]
Message-ID: <PU1PR01MB215558290BACD7A3293F35608D929@PU1PR01MB2155.apcprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <8433ab7e-1540-37ff-e647-8e8da01e07fb@philipmcgrath.com>
On 2021-11-08 20:36 -0500, Philip McGrath wrote:
> On 11/8/21 17:23, Leo Famulari wrote:
> > It will be necessary to fix this issue in the SML/NJ package definition
> > (I think you've done this in a followup patch)
>
> Is this <https://issues.guix.gnu.org/38606>, or somewhere else?
On 2021-11-07, I submitted a patch that can be found at
https://issues.guix.gnu.org/38606, but that patch doesn't fix the
/bin/sh issue. It merely avoids the issue by disabling the building of
SML/NJ libraries. `OS.Process.system` is used during the building of
SML/NJ libraries.
I eventually figured out how to build the whole thing (including
libraries), but it involves using `sed` to patch strings in some
binaries. I will submit a non-WIP patch, hopefully within this week.
By the way, should I submit the new patch to
https://issues.guix.gnu.org/38606 (38606@debbugs.gnu.org), or should I
start a new thread by submitting it to guix-patches@gnu.org?
next prev parent reply other threads:[~2021-11-09 3:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 9:25 How to add /bin/sh to the build environment Foo Chuan Wei
2021-11-08 16:54 ` Xinglu Chen
2021-11-08 20:19 ` Foo Chuan Wei
2021-11-08 22:23 ` Leo Famulari
2021-11-09 1:36 ` Philip McGrath
2021-11-09 3:51 ` Foo Chuan Wei [this message]
2021-11-10 1:41 ` Leo Famulari
2021-11-08 22:58 ` Philip McGrath
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=PU1PR01MB215558290BACD7A3293F35608D929@PU1PR01MB2155.apcprd01.prod.exchangelabs.com \
--to=chuanwei.foo@hotmail.com \
--cc=help-guix@gnu.org \
--cc=philip@philipmcgrath.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.
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).