From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: 12887@debbugs.gnu.org, DNS <dns@rbose.org>
Subject: bug#12887: Broken pipe while generating guile-procedures.texi
Date: Tue, 05 Mar 2013 21:49:21 +0100 [thread overview]
Message-ID: <87boaxh8ry.fsf@gnu.org> (raw)
In-Reply-To: <874ngpu4mh.fsf@pobox.com> (Andy Wingo's message of "Tue, 05 Mar 2013 18:40:38 +0100")
Andy Wingo <wingo@pobox.com> skribis:
> On Fri 07 Dec 2012 22:59, ludo@gnu.org (Ludovic Courtès) writes:
>
>> Ooh, I see. This is related to commit ed4c3739 (see
>> <http://lists.gnu.org/archive/html/guile-devel/2011-12/msg00160.html>).
>>
>> What happens is that the directory name may be correctly decoded when
>> passed as an argument:
>>
>> [ludo@pluto:~/tmp/Courtès]$ strace -f -o ,,s ~/src/guile/meta/guile -L $PWD -c '(set-port-encoding! (current-output-port) "UTF-8")(pk %load-path)'
>>
>> ;;; (("/home/ludo/tmp/Courtès" ...))
>>
>> But then ‘scm_stat’ calls ‘scm_to_locale_string’, which uses the wrong
>> encoding at this point [...]
>
> Nice debugging for a nasty problem.
>
>> So, as mentioned in the thread above, 2.2 will not have this problem.
>> But for 2.0, I can’t even imagine an ugly hack that would help.
>>
>> Thoughts?
>
> What about an environment variable that can tell Guile to do the
> setlocale(). We can set the environment variable during the build so
> that at least the build works, and whisper it to users when they run
> into problems (while noting that the variable will not be read in 2.2).
Yes, sounds like a plan. ‘GUILE_INSTALL_LOCALE’?
> Or should we go ahead and document it, and simply have its default value
> change between 2.0 and 2.2?
Yes, even better, since the setlocale change will have to be documented
at least in NEWS anyway.
Are you willing to look into it?
Ludo’.
next prev parent reply other threads:[~2013-03-05 20:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 19:44 bug#12887: Broken pipe while generating guile-procedures.texi DNS
2012-11-14 23:10 ` Ludovic Courtès
2012-12-07 17:30 ` DNS
2012-12-07 21:59 ` Ludovic Courtès
2013-03-05 17:40 ` Andy Wingo
2013-03-05 20:49 ` Ludovic Courtès [this message]
2013-03-07 10:04 ` Andy Wingo
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=87boaxh8ry.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=12887@debbugs.gnu.org \
--cc=dns@rbose.org \
--cc=wingo@pobox.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).