From: Andy Wingo <wingo@pobox.com>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: bug-guile@gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: Problem generating documentation
Date: Wed, 28 Oct 2009 22:14:53 +0100 [thread overview]
Message-ID: <m3aazbi5ki.fsf@pobox.com> (raw)
In-Reply-To: <873a539qp9.fsf@ossau.uklinux.net> (Neil Jerram's message of "Wed, 28 Oct 2009 21:03:14 +0000")
On Wed 28 Oct 2009 22:03, Neil Jerram <neil@ossau.uklinux.net> writes:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Andy Wingo <wingo@pobox.com> 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 absolutely?
>>
>> 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 old generated one should have been
> deleted by `make distclean', and hence with an invocation of `make
> distclean' (before `git pull' or `git checkout some-other-branch') this
> wouldn't have happened.
Well the one in the $top_builddir wouldn't have been deleted, as it was
moved to $top_builddir/meta.
A
--
http://wingolog.org/
next prev parent reply other threads:[~2009-10-28 21:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 23:57 Problem generating documentation Xan Lopez
2009-10-24 8:55 ` Neil Jerram
2009-10-26 20:59 ` Xan Lopez
2009-10-26 21:16 ` Ludovic Courtès
2009-10-27 21:20 ` Neil Jerram
2009-10-27 23:21 ` Andy Wingo
2009-10-28 8:49 ` Ludovic Courtès
2009-10-28 21:03 ` Neil Jerram
2009-10-28 21:14 ` Andy Wingo [this message]
2009-10-28 22:22 ` 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=m3aazbi5ki.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=ludo@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).