Hello,
"Roberto Belloni" writes:
> [r...@localhost guile-1.8.6]# ./configure
> : bad interpreter: No such file or directory
Normally you have this:
--8<---cut here---start->8---
$ head -1 configure
#! /bin/sh
--8<---cut here---end
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andy Wingo wrote:
> Hi Luca :-)
>
> On Fri 13 Nov 2009 21:24, Luca Saiu writes:
>
>> load should call canonicalize-path relative to the directory of the file
>> which loads the other one, not relative to `pwd`.
>
> Has this changed since 1.8?
Yes,
Hi Thien-Thi,
On Wed 18 Nov 2009 06:16, Thien-Thi Nguyen writes:
> () Andy Wingo
> () Mon, 16 Nov 2009 20:23:07 +0100
>
>However the use case is important. We need to implement a (current-file)
>macro, I think, which should allow for file-relative loads.
>
> Is `current-load-port' still
On Wed 18 Nov 2009 11:05, Luca Saiu writes:
> Andy Wingo wrote:
>> On Fri 13 Nov 2009 21:24, Luca Saiu writes:
>>
>>> load should call canonicalize-path relative to the directory of the file
>>> which loads the other one, not relative to `pwd`.
>>
>> Has this changed since 1.8?
>
> Yes, it has
Andy Wingo writes:
> Hi Thien-Thi,
>
> On Wed 18 Nov 2009 06:16, Thien-Thi Nguyen writes:
>
>> () Andy Wingo
>> () Mon, 16 Nov 2009 20:23:07 +0100
>>
>>However the use case is important. We need to implement a (current-file)
>>macro, I think, which should allow for file-relative loads.
Hi Luca!
I actually looked into it on my trip back from Göteborg, in the hope of
fixing it for 1.9.5, in vain. I did reproduce the problem with
‘DIR/a.scm’ and ‘DIR/b/c.scm’ where ‘c.scm’ contains ‘(load "../a.scm")’.
I first tried to fix it by having ‘load’ prepend the directory name of
the fil
