From: Christoph Garbers <cgarbers@gmx.de>
Subject: Re: Problems with Emacs21 and Oort 0.08
Date: 17 Sep 2002 12:40:40 +0200 [thread overview]
Message-ID: <yw.ld.1032259240.fsf@gabsi.garbers.org> (raw)
In-Reply-To: <ilu8z20di43.fsf@latte.josefsson.org> (Simon Josefsson's message of "Tue, 17 Sep 2002 12:29:32 +0200")
Simon Josefsson wrote:
> This looks like byte compilation error to me. They are usually caused
> by compiling elisp with one flavour of emacs and using it with
> another. Is the gnus package byte compiling gnus correctly for all
> your installed emacsen?
I think so:
,--------
| edoras:/home/gabsi# apt-get install gnus
| Reading Package Lists... Done
| Building Dependency Tree... Done
| 1 packages upgraded, 0 newly installed, 0 to remove and 403 not upgraded.
| Need to get 1721kB of archives. After unpacking 0B will be used.
| Get:1 http://people.debian.org packages/ gnus 5.9.0-0.CVS.2002.09.16.1 [1721kB]
| Fetched 1721kB in 20s (82.8kB/s)
| (Reading database ... 44162 files and directories currently installed.)
| Preparing to replace gnus 5.9.0-0.CVS.2002.09.15.1 (using .../gnus_5.9.0-0.CVS.2002.09.16.1_all.deb) ...
| Unpacking replacement gnus ...
| Setting up gnus (5.9.0-0.CVS.2002.09.16.1) ...
| install/gnus: Ignoring emacs.
| install/gnus: Byte-compiling for emacs20...found emacs20 ..(emacs20 -batch -q -no-site-file -l ./dgnushack.el -f dgnushack-compile)
| done.
| install/gnus: Byte-compiling for emacs21...found emacs21 ..(emacs21 -batch -q -no-site-file -l ./dgnushack.el -f dgnushack-compile)
| done.
`--------
Christoph
next prev parent reply other threads:[~2002-09-17 10:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 22:02 Christoph Garbers
2002-09-17 8:25 ` Frank Schmitt
2002-09-17 10:08 ` Christoph Garbers
2002-09-17 10:29 ` Simon Josefsson
2002-09-17 10:40 ` Christoph Garbers [this message]
2002-09-17 19:41 ` Simon Josefsson
2002-09-17 22:55 ` Christoph Garbers
2002-09-18 8:37 ` Christoph Garbers
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=yw.ld.1032259240.fsf@gabsi.garbers.org \
--to=cgarbers@gmx.de \
/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).