unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Julian Graham <joolean@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: trace examples broken in master
Date: Tue, 22 Sep 2009 20:57:59 +0100	[thread overview]
Message-ID: <87vdjag3aw.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <2bc5f8210909220728y64f338a3sb0cc936a33aacb6@mail.gmail.com> (Julian Graham's message of "Tue, 22 Sep 2009 10:28:47 -0400")

Julian Graham <joolean@gmail.com> writes:

> I've cleared my .cache directory and just finished doing a build from
> master.  My transcript now looks exactly like yours, except that, as
> before, there's no trace output.  Anything else I need to set up
> locally?

Not that I'm aware of!  I just tried the transcript again, with current
master; no change from what I posted before, except that the version is
now 1.9.3, and the stack count incorrect warning has gone.

One detail that I didn't say before: I'm starting Guile by running
`meta/guile -q' from the root directory of my working tree.  It's
possible, if you are starting Guile differently, that you could be
picking up either libraries or Scheme modules from outside the tree, and
hence which might not be up to date.

       Neil




  reply	other threads:[~2009-09-22 19:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 19:22 trace examples broken in master Julian Graham
2009-07-14  8:07 ` Neil Jerram
2009-07-23 21:42   ` Andy Wingo
2009-08-14 17:00     ` Neil Jerram
2009-08-14 17:21       ` Julian Graham
2009-08-30 10:07   ` Neil Jerram
2009-08-30 15:10     ` Julian Graham
2009-09-01 22:16       ` Neil Jerram
2009-09-15 21:54         ` Neil Jerram
2009-09-16  0:55           ` Neil Jerram
2009-09-22 14:28           ` Julian Graham
2009-09-22 19:57             ` Neil Jerram [this message]
2009-09-23  1:34               ` Julian Graham
2009-09-23 20:19                 ` Neil Jerram

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=87vdjag3aw.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-devel@gnu.org \
    --cc=joolean@gmail.com \
    /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).