From: Neil Jerram <neil@ossau.uklinux.net>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: compiling with -DSCM_DEBUG=1
Date: Mon, 16 Nov 2009 20:40:08 +0000 [thread overview]
Message-ID: <87zl6mgq53.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <C681A629-2C16-42F3-AF3D-9916A55C0746@raeburn.org> (Ken Raeburn's message of "Mon, 16 Nov 2009 14:37:31 -0500")
Ken Raeburn <raeburn@raeburn.org> writes:
> On Nov 16, 2009, at 01:08, Ken Raeburn wrote:
>> Andy's just changed a bunch of stuff affecting these files; I've
>> remerged my changes, but I'm not sure if they're needed any more.
>> I'll try to examine this further tomorrow.
>
> I had to run the test suite rather than just finish the build to
> reproduce the failure, but it's still there. After Andy's rearranging
> and rewriting of much code, the eval.i.c patch isn't needed, and the
> code to be changed in objects.c is now in goops.c. My appropriately-
> rearranged patch has been committed...
Top marks for persistence!
Neil
next prev parent reply other threads:[~2009-11-16 20:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 2:06 compiling with -DSCM_DEBUG=1 Ken Raeburn
2009-09-01 19:35 ` Ludovic Courtès
2009-09-03 21:04 ` Ken Raeburn
2009-09-04 22:56 ` Ken Raeburn
2009-09-05 23:42 ` Ken Raeburn
2009-09-06 0:37 ` Ken Raeburn
2009-09-06 8:47 ` Andy Wingo
2009-09-07 9:22 ` Ludovic Courtès
2009-09-09 15:51 ` Ken Raeburn
2009-10-18 22:44 ` Neil Jerram
2009-10-19 13:52 ` Ken Raeburn
2009-10-19 18:47 ` Andy Wingo
2009-10-29 22:16 ` Ken Raeburn
2009-10-30 21:28 ` Neil Jerram
2009-10-31 15:42 ` Neil Jerram
2009-11-14 11:46 ` Andy Wingo
2009-11-14 13:47 ` Neil Jerram
2009-11-14 17:07 ` Ken Raeburn
2009-11-15 4:34 ` Ken Raeburn
2009-11-15 22:25 ` Neil Jerram
2009-11-16 6:08 ` Ken Raeburn
2009-11-16 19:27 ` Andy Wingo
2009-11-16 19:37 ` Ken Raeburn
2009-11-16 20:40 ` Neil Jerram [this message]
2009-11-15 22:10 ` Neil Jerram
2009-10-31 14:39 ` 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=87zl6mgq53.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=raeburn@raeburn.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).