From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Xan Lopez Newsgroups: gmane.lisp.guile.bugs Subject: Re: Problem generating documentation Date: Mon, 26 Oct 2009 22:59:14 +0200 Message-ID: References: <873a59rx0h.fsf@ossau.uklinux.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1256590774 3647 80.91.229.12 (26 Oct 2009 20:59:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 26 Oct 2009 20:59:34 +0000 (UTC) Cc: bug-guile@gnu.org To: Neil Jerram Original-X-From: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Mon Oct 26 21:59:27 2009 Return-path: Envelope-to: guile-bugs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1N2Wez-0005Wk-Qa for guile-bugs@m.gmane.org; Mon, 26 Oct 2009 21:59:26 +0100 Original-Received: from localhost ([127.0.0.1]:57469 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N2Wez-0007Y8-H7 for guile-bugs@m.gmane.org; Mon, 26 Oct 2009 16:59:25 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N2Weu-0007Xp-LN for bug-guile@gnu.org; Mon, 26 Oct 2009 16:59:20 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N2Weq-0007VG-SR for bug-guile@gnu.org; Mon, 26 Oct 2009 16:59:20 -0400 Original-Received: from [199.232.76.173] (port=50005 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N2Weq-0007V8-NZ for bug-guile@gnu.org; Mon, 26 Oct 2009 16:59:16 -0400 Original-Received: from mail-ew0-f228.google.com ([209.85.219.228]:39078) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N2Wep-000051-U6 for bug-guile@gnu.org; Mon, 26 Oct 2009 16:59:16 -0400 Original-Received: by ewy28 with SMTP id 28so5520750ewy.42 for ; Mon, 26 Oct 2009 13:59:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=SEwyPrU+vuxHpLifOWbI94IV4+Ix8gh4/ols57dqPmI=; b=grpvYGdzqikUwAytCCm/eosGdBfO/xqFRj4bzainxVz5ZUmpy6Zp5d1dL3VdJ/OEex gBABh/4gZHvvTUji+lGjhSn1tXK3zY+jcGoyDyfX2BwA7Ko+wkSZWlYsGKHIRHJy858n TO0QyAmcUp1XvXxZHfk6Cw3phx0/rhQZOxR2E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=C+51gPMYtT8CdrgZ78W2PN26YywtkhG8lzQTVgqorjHuaFqA86pwj7LP8x4hyDH/LS 0P/aEI71fxa/+pVqidA/U7zbFR6UKNPbpst9JVTV/+B1igWE7pVSI8Nvi/ldPtMGBxvM wpIuUzgWKv2tCHUrduOu8yDKIOkJxoN0dMoEE= Original-Received: by 10.216.87.79 with SMTP id x57mr16881wee.83.1256590754090; Mon, 26 Oct 2009 13:59:14 -0700 (PDT) In-Reply-To: <873a59rx0h.fsf@ossau.uklinux.net> X-Google-Sender-Auth: f265a47749e26438 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: bug-guile@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GUILE, GNU's Ubiquitous Extension Language" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Errors-To: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.bugs:4350 Archived-At: On Sat, Oct 24, 2009 at 10:55 AM, Neil Jerram wrot= e: > 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 `#! ... !#' com= ment > > If you take a look at /home/xan/git/guile/guile-tools, is the comment > really unterminated (as a Scheme block comment)? =A0There should be > > !# > > on its own on line 4, and that terminates the block comment. 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. If I do a 'git status' git says it does not know anything about that, so I moved it out of the way, did a 'git clean -f', and now things seem to work OK. So I guess we can close the issue unless someone wants to figure out how that file managed to be generated.