From: ludo@gnu.org (Ludovic Courtès)
To: Sree Harsha Totakura <sreeharsha@totakura.in>
Cc: 16463@debbugs.gnu.org, control@debbugs.gnu.org
Subject: bug#16463: Guile derivation fails to build
Date: Fri, 17 Jan 2014 12:08:03 +0100 [thread overview]
Message-ID: <87lhyeyigc.fsf@gnu.org> (raw)
In-Reply-To: <52D90A1B.90600@totakura.in> (Sree Harsha Totakura's message of "Fri, 17 Jan 2014 11:46:51 +0100")
reassign 16463 guile 2.0.9
retitle 16463 ‘file-encoding’ truncates encoding name
thanks
Sree Harsha Totakura <sreeharsha@totakura.in> skribis:
> On 01/17/2014 11:44 AM, Ludovic Courtès wrote:
>> What does this report:
>>
>> ./meta/guile -c '(pk (file-encoding (open-input-file
>> "test-suite/standalone/test-command-line-encoding2")))'
>
> It reports:
>
>> bash-4.2$ meta/guile -c '(pk (file-encoding (open-input-file
>> "test-suite/standalone/test-command-line-encoding2")))' ;;;
>> ("ISO-885")
OK, that’s the problem.
I can reproduce it by changing the shebang to this:
--8<---------------cut here---------------start------------->8---
#!/foo/nix/store/bwjl94kaigsxd64pgzs2j1cj0wn67v76-glibc-2.18/bin/sh
--8<---------------cut here---------------end--------------->8---
This is a bug in Guile’s encoding-cookie scanner: it looks for the
string ‘coding:’ in the first 500 bytes of the file. Here it does find
it and proceeds to read the next token, except that it stops at 500
bytes, thereby truncating the encoding name.
I’ll look for a fix on the Guile side.
In the meantime, I’m afraid there is no nice way to work around it in
your Guix install. You could work around it by using a shorter store
directory name, or you could have a local patch in guile.scm that
changes ‘test-command-line-encoding2’ to read ‘coding: utf-8’...
Thanks,
Ludo’.
prev parent reply other threads:[~2014-01-17 11:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 12:07 bug#16463: Guile derivation fails to build Sree Harsha Totakura
2014-01-16 23:32 ` Ludovic Courtès
2014-01-17 9:16 ` Sree Harsha Totakura
2014-01-17 9:42 ` Sree Harsha Totakura
2014-01-17 10:04 ` Ludovic Courtès
2014-01-17 10:13 ` Sree Harsha Totakura
2014-01-17 10:35 ` Ludovic Courtès
2014-01-17 10:44 ` Ludovic Courtès
2014-01-17 10:46 ` Sree Harsha Totakura
2014-01-17 11:08 ` Ludovic Courtès [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lhyeyigc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=16463@debbugs.gnu.org \
--cc=control@debbugs.gnu.org \
--cc=sreeharsha@totakura.in \
/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).