From: Jay Sulzberger <jays@panix.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Re: `include' relative to current file
Date: Tue, 22 Jan 2013 00:54:48 -0500 (EST) [thread overview]
Message-ID: <Pine.NEB.4.64.1301210449040.21611@panix3.panix.com> (raw)
In-Reply-To: <87ip6q9afx.fsf@pobox.com>
On Mon, 21 Jan 2013, Andy Wingo <wingo@pobox.com> wrote:
> Hi Jay,
Hi, Andy!
>
> On Mon 21 Jan 2013 07:08, Jay Sulzberger <jays@panix.com> writes:
>
>> /usr/share/slib/guile-2.init
>>
>> and made a symlink from /usr/share/slib/guile.init pointing to above file.
>
> FWIW if you use slib from CVS, the included "guile.init" will include
> the "guile-2.init" transparently if you are on Guile 2.0, and fall back
> to the older code otherwise.
I have pulled the latest slib and I see the conditional include
of guile-2.init inside guile.init.
>
>> I still was not able to just start up guile-2.0 and do
>>
>> (use-modules (ice-9 slib))
>>
>> and have slib working.
>
> Seems to work for me. Ah, one thing: you need to update your ice-9/slib.scm
> as well. See commit b194b59fa10574868f7b1663a1f2d447baa18c5e.
>
>> Likely this hard coding of the path to slib's guile.init is not
>> the right way to repair the guile-slib system.
>
> Not sure. You could install slib to the load path. On Debian systems,
> the hacks from b194b59fa10574868f7b1663a1f2d447baa18c5e will work. On
> other systems, I guess we'll get bug reports :)
>
> Cheers,
>
> Andy
I have pulled the latest guile and though I have not yet checked
that commit, I have seen the latest code in slib.scm and it is
better than my hard-code-the-path fix.
I will look and see if I can figure out how %load-path and
load-from-path and allied stuff works.
Thank you, Guile team!
oo--JS.
> --
> http://wingolog.org/
>
>
next prev parent reply other threads:[~2013-01-22 5:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 19:28 `include' relative to current file Andy Wingo
2013-01-20 19:57 ` Jay Sulzberger
2013-01-21 6:08 ` Jay Sulzberger
2013-01-21 9:01 ` Andy Wingo
2013-01-22 5:54 ` Jay Sulzberger [this message]
2013-01-22 10:16 ` Ludovic Courtès
2013-01-22 11:09 ` 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=Pine.NEB.4.64.1301210449040.21611@panix3.panix.com \
--to=jays@panix.com \
--cc=guile-devel@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).