On Wed 28 Oct 2009 22:03, Neil Jerram writes:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Andy Wingo writes:
>>
>>> I think the deal was that it used to be generated, and in the root. But
>>> I changed it to be not generated, and in the meta/. But this error was
>>> coming from Scheme; perhaps
Hi,
Neil Jerram writes:
> l...@gnu.org (Ludovic Courtès) writes:
[...]
>> Yes, I think so. It’s run as “./meta/uninstalled-env guile-tools” and
>> somehow it seems that $top_builddir ended up before $top_builddir/meta
>> in $PATH (don’t ask me why :-)).
>
> Hmm, it still seems to me that the
l...@gnu.org (Ludovic Courtès) writes:
> Hi,
>
> Andy Wingo writes:
>
>> I think the deal was that it used to be generated, and in the root. But
>> I changed it to be not generated, and in the meta/. But this error was
>> coming from Scheme; perhaps there was a issue with load path issue
>> where
Hi,
Andy Wingo writes:
> I think the deal was that it used to be generated, and in the root. But
> I changed it to be not generated, and in the meta/. But this error was
> coming from Scheme; perhaps there was a issue with load path issue
> whereby guile-tools was loaded from a path and not abso
Hi,
On Tue 27 Oct 2009 22:20, Neil Jerram writes:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Hello,
>>
>> Xan Lopez writes:
>
>>> Ok, the problem is that I had a file named "guile-tools" in the
>>> toplevel, which was a shell script and had nothing to do with
>>> meta/guile-tools (no idea ho
l...@gnu.org (Ludovic Courtès) writes:
> Hello,
>
> Xan Lopez writes:
>> Ok, the problem is that I had a file named "guile-tools" in the
>> toplevel, which was a shell script and had nothing to do with
>> meta/guile-tools (no idea how it got there...), which is what I assume
>> you were talking
Hello,
Xan Lopez writes:
> On Sat, Oct 24, 2009 at 10:55 AM, Neil Jerram wrote:
>> Xan Lopez writes:
>>
>>> Hi,
>>>
>>> Using commit 32b12f40509e4bcb0823e1bb2a57e50af14560b5, I get the
>>> following error when the doc is being generated:
>>
>>> ERROR: In procedure skip_block_comment:
>>> ERROR
On Sat, Oct 24, 2009 at 10:55 AM, Neil Jerram wrote:
> Xan Lopez writes:
>
>> Hi,
>>
>> Using commit 32b12f40509e4bcb0823e1bb2a57e50af14560b5, I get the
>> following error when the doc is being generated:
>
>> ERROR: In procedure skip_block_comment:
>> ERROR: /home/xan/git/guile/guile-tools:1:3:
Xan Lopez writes:
> Hi,
>
> Using commit 32b12f40509e4bcb0823e1bb2a57e50af14560b5, I get the
> following error when the doc is being generated:
> ERROR: In procedure skip_block_comment:
> ERROR: /home/xan/git/guile/guile-tools:1:3: unterminated `#! ... !#' comment
If you take a look at /home/xa
Hi,
Using commit 32b12f40509e4bcb0823e1bb2a57e50af14560b5, I get the
following error when the doc is being generated:
make[3]: Entering directory `/home/xan/git/guile/libguile'
cat alist.doc arbiters.doc array-handle.doc array-map.doc arrays.doc
async.doc backtrace.doc boolean.doc bitvectors.doc
10 matches
Mail list logo