From: Keisuke Nishida <kxn30@po.cwru.edu>
To: Kalle Olavi Niemitalo <tosi@ees2.oulu.fi>
Cc: guile-emacs@sourceware.cygnus.com
Subject: Re: guileapi.x problems [patch]
Date: Thu, 16 Mar 2000 08:55:00 -0000 [thread overview]
Message-ID: <m31z5a26tt.fsf@kei.cwru.edu> (raw)
In-Reply-To: <87u2i7yzy8.fsf@PC486.Niemitalo.LAN>
Kalle Olavi Niemitalo <tosi@ees2.oulu.fi> writes:
> > A suggestion: Redirect output to guileapi.tmp, then rename that file
> > to guileapi.x.
>
> That is what I tried initially, but it didn't work. guileapi.c
> #includes guileapi.x and if it doesn't exist, guile-snarf complains.
>
> Perhaps the #include should be wrapped in #ifndef SCM_MAGIC_SNARFER.
> Is guile-snarf guaranteed to keep defining that?
This is what guile-snarf does:
## We must use a temporary file here, instead of a pipe, because we
## need to know if CPP exits with a non-zero status.
${CPP} -DSCM_MAGIC_SNARFER "$@" > ${temp} || exit $?
And this is how Guile's Makefile call it:
.c.x:
PATH=.:${PATH} ./guile-doc-snarf $< $(DEFS) $(INCLUDES) $(CPPFLAGS) $(CFLAGS) $< > $@ \
|| { rm $@; false; }
What would be the best?
next prev parent reply other threads:[~2000-03-16 8:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-13 15:11 guile-emacs-0.1 released Keisuke Nishida
2000-03-14 12:46 ` guileapi.x problems [patch] Kalle Olavi Niemitalo
2000-03-14 13:20 ` Keisuke Nishida
2000-03-15 21:11 ` Ken Raeburn
2000-03-16 4:29 ` Kalle Olavi Niemitalo
2000-03-16 8:55 ` Keisuke Nishida [this message]
2000-03-16 16:57 ` Kalle Olavi Niemitalo
2000-03-17 9:55 ` Keisuke Nishida
2000-03-15 21:07 ` guile-emacs-0.1 released Ken Raeburn
2000-03-16 12:29 ` Keisuke Nishida
2000-03-16 18:50 ` Richard Stallman
2000-03-17 2:10 ` Ken Raeburn
2001-01-07 9:13 ` Richard Stallman
2001-01-07 13:28 ` Ken Raeburn
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m31z5a26tt.fsf@kei.cwru.edu \
--to=kxn30@po.cwru.edu \
--cc=guile-emacs@sourceware.cygnus.com \
--cc=tosi@ees2.oulu.fi \
/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).