From: Rob Browning <rlb@defaultvalue.org>
Cc: ttn@glug.org, guile-devel@gnu.org
Subject: Re: snarfer guard macro name decision: SCM_MAGIC_SNARFER
Date: Thu, 21 Mar 2002 10:23:23 -0600 [thread overview]
Message-ID: <87u1r951qc.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87elif0wt2.fsf@zagadka.ping.de> (Marius Vollmer's message of "20 Mar 2002 22:11:05 +0100")
Marius Vollmer <mvo@zagadka.ping.de> writes:
>> No problem. Thanks for letting me know, though -- just holler when
>> you get a chance to finish.
>
> Ok, I've committed something. Please check.
I'm trying to check against some of the other projects that use
guile-snarf, and I wanted to make sure I knew how things are expected
to work now (it's OK if the other projects need to change their
source, I just want to make sure I knew what those changes are and
that they're in NEWS and/or info).
Here's what gnome-guile 0.21pre4's failing on with current 1.5 cvs --
if I run the make immediately again, it seems to proceed normally, so
I'm presuming there's still some "file existence race" or similar:
make[2]: Entering directory `/home/rlb/dev/guile/check/src/gnome-guile-0.21pre4/guile-gtk'
guile-snarf -DHAVE_CONFIG_H -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include -I/home/rlb/dev/guile/check/src/gnome-guile/guile-gtk -I/home/rlb/dev/guile/check/tmp/include -I/home/rlb/dev/guile/check/tmp/include -I/home/rlb/dev/guile/check/tmp/include -g -O2 gtk-support.c >gtk-support.x
make[2]: *** [gtk-support.x] Error 1
make[2]: Leaving directory `/home/rlb/dev/guile/check/src/gnome-guile-0.21pre4/guile-gtk'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/rlb/dev/guile/check/src/gnome-guile-0.21pre4'
make: *** [all] Error 2
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-21 16:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 7:51 snarfer guard macro name decision: SCM_MAGIC_SNARFER Thien-Thi Nguyen
2002-03-13 9:26 ` Thien-Thi Nguyen
2002-03-13 19:15 ` Marius Vollmer
2002-03-13 21:28 ` Thien-Thi Nguyen
2002-03-13 22:00 ` Rob Browning
2002-03-13 22:58 ` Thien-Thi Nguyen
2002-03-14 0:12 ` Thien-Thi Nguyen
2002-03-14 5:44 ` Rob Browning
2002-03-14 18:48 ` Marius Vollmer
2002-03-14 20:44 ` Thien-Thi Nguyen
2002-03-14 23:35 ` Marius Vollmer
2002-03-15 4:26 ` Thien-Thi Nguyen
2002-03-15 15:56 ` Thien-Thi Nguyen
2002-03-15 21:19 ` Marius Vollmer
2002-03-14 5:56 ` Thien-Thi Nguyen
2002-03-14 6:58 ` Rob Browning
2002-03-14 7:17 ` Rob Browning
2002-03-14 9:32 ` Thien-Thi Nguyen
2002-03-14 23:40 ` Marius Vollmer
2002-03-14 19:09 ` Marius Vollmer
2002-03-14 22:43 ` Thien-Thi Nguyen
2002-03-14 23:31 ` Rob Browning
2002-03-15 21:12 ` Marius Vollmer
2002-03-15 21:33 ` Rob Browning
2002-03-15 21:58 ` Marius Vollmer
2002-03-17 17:07 ` Rob Browning
2002-03-18 0:07 ` Marius Vollmer
2002-03-18 2:52 ` Rob Browning
2002-03-20 21:11 ` Marius Vollmer
2002-03-21 16:23 ` Rob Browning [this message]
2002-04-24 20:07 ` Marius Vollmer
2002-04-24 20:42 ` Rob Browning
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=87u1r951qc.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
--cc=ttn@glug.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).