From: David Abrahams <dave@boost-consulting.com>
Subject: Re: "Can't read partial active file"
Date: Fri, 09 Jan 2004 20:36:02 -0500 [thread overview]
Message-ID: <8ykg4mbh.fsf@boost-consulting.com> (raw)
In-Reply-To: <microsoft-free.87wu80etih.fsf@eicq.dnsalias.org>
Steve Youngs <sryoungs@bigpond.net.au> writes:
> |--==> "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]
I haven't been using make, but I have been using two separate gnus CVS
images for Gnu and X emacs in order to keep the bytecode separate.
It's always worked until now.
Is there a make command I can use to build Gnus for non-Cygwin
installations of [X]emacs on Windows?
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
next prev parent reply other threads:[~2004-01-10 1:36 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
2004-01-10 1:36 ` David Abrahams [this message]
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=8ykg4mbh.fsf@boost-consulting.com \
--to=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).