From: Jake Colman <colman@ppllc.com>
Subject: Re: More Build Problems
Date: 10 Feb 1998 17:22:18 -0500 [thread overview]
Message-ID: <764t279k2t.fsf@clay.principia.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 10 Feb 1998 21:55:04 +0100
>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
LMI> Jake Colman <colman@ppllc.com> writes: This means that your cl.el was
LMI> compiled for Emacs 19.29 or later. So you should use Emacs 19.29 or
LMI> later when compiling.
>> Look at my email header: X-Mailer: Gnus v5.5/Emacs 20.2
>>
>> My initial posting including the output of (emacs-version):
>>
>> GNU Emacs 20.2.1 (sparc-sun-solaris2.4, X toolkit) of Mon Dec 1 1997 on
>> clay.principia.com
>>
>> Am I missing something obvious? 'cause I'm starting to feel really dumb!
LMI> Apparently the Emacs you're using when compiling isn't the same as
LMI> you're using when reading. For some reason or other.
For reasons that totally escape me, unless I fully qualify EMACS to point to
the emacs in my ~/bin directory, it is finding the SA-installed version which
is an earlier version. This is happening even though my version of emacs is in
my PATH prior to the SA version.
Go figure...
--
Jake Colman
Principia Partners LLC | Phone: (201) 946-0300
Harborside Financial Center | Fax: (201) 946-0320
902 Plaza II | Beeper: (800) 505-2795
Jersey City, NJ 07311 | E-mail: colman@ppllc.com
| web: http://www.ppllc.com
prev parent reply other threads:[~1998-02-10 22:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-09 15:59 New Tester: make errors on custom Jake Colman
1998-02-10 10:15 ` Lars Magne Ingebrigtsen
1998-02-10 14:17 ` More Build Problems Jake Colman
1998-02-10 19:11 ` Lars Magne Ingebrigtsen
1998-02-10 19:58 ` Jake Colman
1998-02-10 20:55 ` Lars Magne Ingebrigtsen
1998-02-10 22:22 ` Jake Colman [this message]
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=764t279k2t.fsf@clay.principia.com \
--to=colman@ppllc.com \
/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).