From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Cc: guile-devel@gnu.org
Subject: Re: GNU Guile 1.9.5 released (alpha)
Date: Wed, 18 Nov 2009 12:23:29 +0100 [thread overview]
Message-ID: <87ocn0rs9a.fsf@gnu.org> (raw)
In-Reply-To: 87pr7genzj.fsf@gnu.org
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
Hello Guilers!
Of course, it was not until this morning that I discovered this:
--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> %load-compiled-path
$1 = ("/home/ludo/soft/lib/GNU Guile/1.9/ccache")
scheme@(guile-user)> %load-path
$2 = ("/home/ludo/.nix-profile/share/guile/site" "/home/ludo/soft/share/GNU Guile/site" "/home/ludo/soft/share/GNU Guile/1.9" "/home/ludo/soft/share/GNU Guile")
$ ls ~/soft/share/GNU\ Guile/1.9/
guile-procedures.txt ice-9/ lang/ language/ oop/ rnrs/ scripts/ srfi/ system/
--8<---------------cut here---------------end--------------->8---
The directory names contain “GNU Guile” instead of “guile”. On
GNU/Linux at least, the build system and Guile don’t have any problems
dealing with whitespaces in directory names, so it actually works, but
it surely wasn’t intended.
I fixed it in ‘master’ and started looking for someone else to blame:
http://git.sv.gnu.org/cgit/guile.git/commit/?id=53da7372beca90a58b7401a84627815289a53d11
http://thread.gmane.org/gmane.comp.sysutils.automake.bugs/4803
Apologies for the inconvenience, and happy GNU\ Guile hacking
nevertheless!
Ludo’.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-11-18 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 23:21 GNU Guile 1.9.5 released (alpha) Ludovic Courtès
2009-11-18 11:23 ` Ludovic Courtès [this message]
2009-11-29 2:45 ` Linas Vepstas
2009-11-29 6:07 ` Linas Vepstas
2009-11-29 12:33 ` Ludovic Courtès
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=87ocn0rs9a.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--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).