From: "David Arroyo" <david@aqwari.net>
To: help-guix@gnu.org
Subject: Re: Defining a toolchain with musl libc
Date: Tue, 12 Apr 2022 14:22:36 -0400 [thread overview]
Message-ID: <c16455aa-467e-4449-9b43-084c74ab09a5@www.fastmail.com> (raw)
In-Reply-To: <a5bba180-9e5a-4461-9c22-de28bb248642@www.fastmail.com>
On Mon, Apr 11, 2022, at 22:34, David Arroyo wrote:
> error: in phase 'patch-source-shebangs': uncaught exception:
> encoding-error "scm_to_stringn" "cannot convert narrow string to
> output locale" 84 #f #f
Looking further into this error, errno 84 is EILSEQ, "illegal byte
sequence". The error is raised during the 'patch-source-shebangs' phase,
while patching ./gcc/testsuite/gdc.test/compilable/test13512.d This
file has the shebang
#!/opt/dmd/ÐÒÏÂÙ/rdmd
This in turn seems to be tripping up this line in guix/build/utils.scm:1094 :
(and=> (and line (regexp-exec shebang-rx line))
I'm not sure why I don't hit this error when building gcc-toolchain.
Perhaps there is different locale information in the build environment
without glibc.
David
next prev parent reply other threads:[~2022-04-12 18:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 2:34 Defining a toolchain with musl libc David Arroyo
2022-04-12 18:22 ` David Arroyo [this message]
2022-05-09 17:09 ` zimoun
2022-05-09 23:54 ` David Arroyo
2022-05-10 8:00 ` zimoun
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=c16455aa-467e-4449-9b43-084c74ab09a5@www.fastmail.com \
--to=david@aqwari.net \
--cc=help-guix@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.
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).