Gnus development mailing list
 help / color / mirror / Atom feed
From: Lloyd Zusman <ljz@asfast.com>
Cc: Kai.Grossjohann@CS.Uni-Dortmund.DE
Subject: Re: Problem with the latest CVS build
Date: 05 Dec 1999 18:24:07 -0500	[thread overview]
Message-ID: <ltu2lx6kfc.fsf@asfast.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "05 Dec 1999 23:58:34 +0100"


[ I'm sorry for this re-post, but the I sent out the previous attempt
  before it was finished. ]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Lloyd Zusman <ljz@asfast.com> writes:
> 
> > Well, I'm using XEmacs, which means that `mailheader' is part of its
> > `gnus' package.  But I'm not using the XEmacs distribution of gnus,
> > but rather, the CVS version.  Therefore, I don't have access to
> > `mailheader'.
> 
> Why don't you install the normal Gnus package and then add the CVS
> Gnus?  Just put the CVS Gnus directory first in load-path, and Bob
> will be your uncle.

I have done exactly that, but the standard building procedure that
gets downloaded with CVS doesn't know about my normal load path, and
it can't find mailheader in the load path that *it* tries to use.

As far as I know (and someone please correct me if I'm wrong), the
normal way for building an XEmacs-based CVS release goes like this,
starting after the latest CVS update has completed:

(1)  `cd' to the `gnus' subdirectory of the CVS tree.

(2)  Do this ...

       ./configure
       make EMACS=xemacs

The `make' step causes the following command to get executed:

  xemacs -batch -q -no-site-file -l ./dgnushack.el -f dgnushack-compile

The `-q' and `-no-site-file' options ensure that my own startup and
initialization files don't get loaded during this build.  Therefore,
there is no way for my own load path to be recognized during the
build.

That's the reason why `mailheader' and `timer' are not getting found
during the XEmacs build unless I actually put copies of them into
the `gnus/lisp' subdirectory.

There don't seem to be any options for `configure' or in any of the
makefiles which allow extra directories to be added to the load
path during the build.  This is why I suggested that perhaps
one or more of these files get changed so we could optionally
specify one or more directories to be added to these paths
during the Gnus build.

Any ideas?

Thanks in advance.

-- 
 Lloyd Zusman
 ljz@asfast.com


  parent reply	other threads:[~1999-12-05 23:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-04  8:12 Daniel Pittman
1999-12-04  8:31 ` Lars Magne Ingebrigtsen
1999-12-04  8:40   ` Daniel Pittman
1999-12-04  9:02     ` Shenghuo ZHU
1999-12-04 11:18       ` Mike Fabian
1999-12-04 13:27       ` William M. Perry
1999-12-05  0:21         ` Dave Love
1999-12-05  0:19       ` Dave Love
1999-12-05  1:45       ` Lloyd Zusman
1999-12-05  8:38         ` Hans de Graaff
1999-12-05 18:28           ` Lloyd Zusman
1999-12-05 18:41             ` Lloyd Zusman
1999-12-05 21:02               ` Hans de Graaff
1999-12-06 17:44                 ` Hrvoje Niksic
1999-12-06 19:13             ` Jan Vroonhof
     [not found]             ` <ltr9h1s01u.fsf@ <byhfhvubli.fsf@urysohn.math.ethz.ch>
1999-12-07  8:20               ` Hrvoje Niksic
1999-12-07 12:27             ` Jan Vroonhof
1999-12-05 22:58         ` Kai Großjohann
1999-12-05 23:03           ` Lloyd Zusman
1999-12-05 23:24           ` Lloyd Zusman [this message]
1999-12-06 10:33             ` Gunnar Evermann
1999-12-06 15:48               ` Lloyd Zusman
1999-12-06 22:42                 ` Kai Großjohann

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=ltu2lx6kfc.fsf@asfast.com \
    --to=ljz@asfast.com \
    --cc=Kai.Grossjohann@CS.Uni-Dortmund.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).