Gnus development mailing list
 help / color / mirror / Atom feed
From: Vin Shelton <acs@xemacs.org>
Subject: Building gnus 5.8.3+ on XEmacs
Date: 01 May 2000 23:05:22 -0400	[thread overview]
Message-ID: <m2ya5tird9.fsf@zion.rcn.com> (raw)

Sorry for a perhaps stupid question.

How do XEmacs users build recent gnus packages under XEmacs?  Since
5.8.3 and up through the current CVS version, building gnus fails
because I don't have timer.el (which lives in fsf-compat) installed.
I do have a workaround, because it so happens I have a full XEmacs
packages build tree, so I can just set EMACSLOADPATH to point to the
built location of the fsf-compat package, and I can then build,
install and run gnus.  Do I need the fsf-compat package at run-time?
It appears not, but why do I need it at compile time?

I dimly recall this issue's having been discussed on the ding list,
and I thought someone was planning on removing / reworking this
dependency to be more XEmacs-friendly.

TIA,
  vin



                 reply	other threads:[~2000-05-02  3:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=m2ya5tird9.fsf@zion.rcn.com \
    --to=acs@xemacs.org \
    /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).