public inbox for guile-emacs@sourceware.org
 help / color / mirror / Atom feed
From: Kalle Olavi Niemitalo <tosi@stekt.oulu.fi>
To: Keisuke Nishida <kxn30@po.cwru.edu>
Cc: guile-emacs@sourceware.cygnus.com
Subject: guileapi.x problems [patch]
Date: Tue, 14 Mar 2000 12:46:00 -0000	[thread overview]
Message-ID: <87og8hp9n8.fsf@PC486.Niemitalo.LAN> (raw)
In-Reply-To: <m31z5e4ga4.fsf@kei.cwru.edu>

I've spent the evening with guile-emacs-0.1 and it's wonderful!
You wrote it needs Emacs 20.6 but version 20.5 seems to work just
fine, at least on i486-debian-linux-gnu.  (Debian doesn't have
20.6 yet.)

There were some problems generating guileapi.x, though:

* I was compiling in a separate directory.  The makefile tried to
  find guileapi.c in the build directory.

* I have the current Guile headers in ~/include, not
  /usr/include.  Using them requires the -I/home/kalle/include
  option, which I have in $CPPFLAGS.  The snarfing rule didn't
  use that variable.

* When the command failed, a zero-length guileapi.x was left.
  The first time this happened, I didn't notice and spent some
  time wondering why emacs-eval didn't work.

=================================================================
--- src/Makefile.in.orig	Tue Mar 14 14:13:42 2000
+++ src/Makefile.in	Tue Mar 14 16:13:15 2000
@@ -1128,8 +1128,14 @@
 sunfns.o: sunfns.c buffer.h window.h $(config_h)
 
 guileapi.o: guileapi.c guileapi.x
+/* Don't leave an empty guileapi.x if guile-snarf fails.
+   OTOH, guileapi.x must exist when guile-snarf runs.
+   The -I options are needed for config.h when $(srcdir) is
+   somewhere else.  This can't use $(ALL_CFLAGS) because
+   guile-snarf may run the preprocessor directly.  */
 guileapi.x: guileapi.c
-	guile-snarf guileapi.c > guileapi.x
+	guile-snarf -I. -I$(srcdir) $(CPPFLAGS) $(srcdir)/guileapi.c > guileapi.x \
+	  || ( rm guileapi.x; false )
 
 ${libsrc}emacstool: ${libsrc}emacstool.c
 	cd ${libsrc}; ${MAKE} ${MFLAGS} emacstool
=================================================================

  reply	other threads:[~2000-03-14 12:46 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 ` Kalle Olavi Niemitalo [this message]
2000-03-14 13:20   ` guileapi.x problems [patch] Keisuke Nishida
2000-03-15 21:11   ` Ken Raeburn
2000-03-16  4:29     ` Kalle Olavi Niemitalo
2000-03-16  8:55       ` Keisuke Nishida
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=87og8hp9n8.fsf@PC486.Niemitalo.LAN \
    --to=tosi@stekt.oulu.fi \
    --cc=guile-emacs@sourceware.cygnus.com \
    --cc=kxn30@po.cwru.edu \
    /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).