unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: ludo@gnu.org (Ludovic Courtès)
Cc: bug-guile@gnu.org
Subject: Re: Problem generating documentation
Date: Tue, 27 Oct 2009 21:20:25 +0000	[thread overview]
Message-ID: <8763a0lejq.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <878wexyhyn.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 26 Oct 2009 22:16:00 +0100")

ludo@gnu.org (Ludovic Courtès) writes:

> Hello,
>
> Xan Lopez <xan@gnome.org> 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 about.

Cool, thanks for closing the loop on this.

> I just hit that too.  The stale $top_builddir/guile-tools typically
> comes from ‘branch_release-1-8’ or from a very old build of ‘master’.

But is it cleaned by make distclean?  I would guess so, since I
regularly switch between branches, using make distclean, and have never
seen this.

If make distclean does clean it, I don't think we need anything else -
unless someone wants to propose a patch to HACKING to cover this.

   Neil




  reply	other threads:[~2009-10-27 21:20 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 [this message]
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
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=8763a0lejq.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=bug-guile@gnu.org \
    --cc=ludo@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).