From: Ben Sima <ben@bsima.me>
To: guile-user@gnu.org
Subject: Re: guild compile unknown character name ??
Date: Mon, 23 Nov 2020 22:34:11 -0500 [thread overview]
Message-ID: <m27dqbig24.fsf@bsima.me> (raw)
In-Reply-To: <87pnb3obdj.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Kovacsics Róbert <kovirobi@gmail.com> skribis:
>
>> /nix/store/6vazrblhsyafnn13iwj6mc9gg6cf8pjv-guile-2.2.7/bin/guild
>> failed:
>> ;;; failed to create path for auto-compiled file
>> "/nix/store/6vazrblhsyafnn13iwj6mc9gg6cf8pjv-guile-2.2.7/bin/guild"
>> ice-9/boot-9.scm:752:25: In procedure dispatch-exception:
>> In procedure scm_lreadr: #<unknown port>:410:18: unknown character name ??
>> make: *** [Makefile:763: inspekt3d/library.go] Error 1
>
> Could you check what’s in inspekt3d/library.scm, line 410, column 18?
>
> This error happens in a character literal with an invalid name
There is no line 410 of inspekt3d/library.scm.
I ran into this same problem while writing a nix expression for
inspekt3d. What fixed it for me was adding glibcLocales to buildInputs.
prev parent reply other threads:[~2020-11-24 3:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 21:09 guild compile unknown character name ?? Kovacsics Róbert
2020-05-16 20:47 ` Ludovic Courtès
2020-11-24 3:34 ` Ben Sima [this message]
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m27dqbig24.fsf@bsima.me \
--to=ben@bsima.me \
--cc=guile-user@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).