From: Makoto Fujiwara <makoto@komekome.bay.prug.or.jp>
Subject: Re: (Emacs-20.2) Symbol's function definition is void ((caddr))
Date: Thu, 09 Oct 1997 06:14:27 +0900 [thread overview]
Message-ID: <19971009061427U.makoto@komekome.bay.prug.or.jp> (raw)
In-Reply-To: <19971008002803P.makoto@komekome.bay.prug.or.jp>
(Just to clarify my previous question with the same Subject),
Some one asking me my Emacs is in strange location and wondering
if I am invoking the right own. Sorry not mentioning to that point.
But I always set path = ( /usr/local/emacs-20.2/bin $path )
and if I ask which emacs, shell says /usr/local/emacs-20.2/bin/emacs.
n> I have noticed that your emacs is at a non-standard location. You
n> don't specify which emacs to use for the building process, are you
n> sure you are picking up the right one?
n> Try:
n> make EMACS=/usr/local/emacs-20.2/bin/emacs
Thanks for reading,
---
(Makoto Fujiwara)
next prev parent reply other threads:[~1997-10-08 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-07 15:28 Makoto Fujiwara
1997-10-08 21:14 ` Makoto Fujiwara [this message]
1997-10-12 21:51 ` Lars Magne Ingebrigtsen
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=19971009061427U.makoto@komekome.bay.prug.or.jp \
--to=makoto@komekome.bay.prug.or.jp \
/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 NNTP newsgroup(s).