From: Steinar Bang <sb@metis.no>
Subject: Re: Cannot open load file" "timer", when byte compiling
Date: 15 Dec 1999 15:05:04 +0100 [thread overview]
Message-ID: <whwvqgpaen.fsf@viffer.oslo.metis.no> (raw)
In-Reply-To: Hrvoje Niksic's message of "06 Dec 1999 15:04:24 +0100"
>>>>> Hrvoje Niksic <hniksic@iskon.hr>:
> John Markus Bjorndalen <johnm@cs.uit.no> writes:
>> Steinar Bang <sb@metis.no> writes:
>>
>> [..]
>> > While compiling toplevel forms in file /home/sb/src/install/gnus/lisp/nnvirtual.el:
>> > !! File error (("Cannot open load file" "timer"))
>> [..]
>>
>> Quick-and-dirty-fix: I just grabbed timer.el from the Emacs 20.4
>> distribution that came with RedHat 6.1 and dropped it in with the
>> gnus source. XEmacs 20.4 didn't come with a timer.el.
> No no no no no! Don't do that. timer.el from FSF Emacs will _not_
> work with XEmacs.
> A real quick&dirty fix would be to get the "fsf-compat" XEmacs
> package, which includes a timer.el implementation that uses itimers.
But where do I find fsf-compat?
Google found me
http://dev.linuxppc.org/RPMS/users-gdt/noarch/xemacs_package-fsf-compat-1.05-1a.noarch.html
which would work for me with SuSE 6.2, but none of the ftp URLs to the
actual RPMs are working.
I did not find anything about fsf-compat on http://www.xemacs.org/
I did find something on rpmfind.net...
http://rpmfind.net/linux/RPM/powertools/6.1/sparc/usr_lib_xemacs_xemacs-packages_lisp_fsf-compat_Tree.html
but quite _what_ this was, I'm not sure.
next prev parent reply other threads:[~1999-12-15 14:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-06 10:03 Steinar Bang
1999-12-06 13:59 ` John Markus Bjorndalen
1999-12-06 14:04 ` Hrvoje Niksic
1999-12-06 16:31 ` Steinar Bang
1999-12-15 14:05 ` Steinar Bang [this message]
1999-12-17 9:50 ` Jan Vroonhof
1999-12-06 22:53 ` Kai Großjohann
1999-12-06 22:56 ` Kai Großjohann
1999-12-07 12:39 ` John Markus Bjorndalen
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=whwvqgpaen.fsf@viffer.oslo.metis.no \
--to=sb@metis.no \
/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).