Gnus development mailing list
 help / color / mirror / Atom feed
From: Steve Youngs <sryoungs@bigpond.net.au>
Cc: David Abrahams <dave@boost-consulting.com>
Subject: Re: "Can't read partial active file"
Date: Sat, 10 Jan 2004 06:50:30 +1000	[thread overview]
Message-ID: <microsoft-free.87wu80etih.fsf@eicq.dnsalias.org> (raw)
In-Reply-To: <zncxrpi5.fsf@boost-consulting.com> (David Abrahams's message of "Fri, 09 Jan 2004 12:38:42 -0500")

[-- Attachment #1: Type: text/plain, Size: 1593 bytes --]

|--==> "DA" == David Abrahams <dave@boost-consulting.com> writes:

  DA> David Abrahams <dave@boost-consulting.com> writes:
  >>After updating Gnus from CVS this morning and byte-recompiling it with

[...]

  DA> Note: this makes Gnus completely unusable under Gnu emacs; I can't
  DA> enter any groups.  It works great under XEmacs, though.  What could
  DA> the problem be?

I don't know if any of what I'm about to mention will fix your
problems, but I'd like to point out a couple of things that I hope you
are already aware of...

  o When building Gnus you should always do so via `make'.  By just
    byte-recompiling the lisp directory you will, amongst other
    things, be missing out on re-building the autoloads (which could
    have changed since your last build).

  o A Gnus built with GNU/Emacs _*CAN NOT*_ be used in XEmacs and vice
    verse.  The two Emacsen generate different incompatible
    byte-code. [1] 

  o If there are things in contrib/ that you want, symlink, copy, or
    move them into the lisp/ directory prior to running `make'.


Footnotes: 
[1]  If you run both GNU/Emacs and XEmacs their respective load-path's
     shouldn't overlap.  Or if you do have directories common to both
     Emacsen's load-path, those directories shouldn't contain any
     byte-compiled lisp.  It's just not worth the trouble.

-- 
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|              Ashes to ashes, dust to dust.               |
|      The proof of the pudding, is under the crust.       |
|------------------------------<sryoungs@bigpond.net.au>---|

[-- Attachment #2: Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2004-01-09 20:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09 15:39 David Abrahams
2004-01-09 17:38 ` David Abrahams
2004-01-09 20:50   ` Steve Youngs [this message]
2004-01-10  1:36     ` David Abrahams
2004-01-10  2:10       ` Jesper Harder

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=microsoft-free.87wu80etih.fsf@eicq.dnsalias.org \
    --to=sryoungs@bigpond.net.au \
    --cc=dave@boost-consulting.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).