From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Gnus doesn't compile anymore
Date: Sun, 21 Oct 2001 11:23:44 +0200 [thread overview]
Message-ID: <vafbsj1fisf.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <7ktpv0j6.fsf@hschmi22.userfqdn.rz-online.de> (Frank Schmitt's message of "Sun, 21 Oct 2001 10:51:25 +0200")
Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:
> Since yesterday Gnus won't compile anymore using the MS Windows
> make*.bat files. XEmacs gives an error message:
>
> Cannot open load file: c:\Programme\cygwin\usr\src\gnus\lpath.el
> xemacs exiting
At this spot, the current working directory should be the lisp
subdir. Is this also the case? (See the code in dgnushack.el; it
assumes this.)
Hm. Maybe the cwd is wrong during building the info files?
kai
--
Lisp is kinda like tpircstsoP
prev parent reply other threads:[~2001-10-21 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-21 8:51 Frank Schmitt
2001-10-21 9:23 ` Kai Großjohann [this message]
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=vafbsj1fisf.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.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).