From: Max Kliche <max@kliche.org>
Cc: ding@gnus.org
Subject: Re: compilation error
Date: 12 Feb 2001 18:44:08 +0100 [thread overview]
Message-ID: <m3d7cnzthz.fsf@kliche.org> (raw)
In-Reply-To: <2nzoft8e4s.fsf@tiger.jia.vnet> (ShengHuo ZHU's message of "11 Feb 2001 09:53:39 -0500")
ShengHuo ZHU <zsh@cs.rochester.edu> wrote:
> NAGY Andras <nagya@inf.elte.hu> writes:
>> [ error ]
> I can not reproduce it with XEmacs 21.2.42 + Sumo tar ball 2001-02-04.
> Are you use it in M$ Windows?
I've got this error (gnus cvs this moment and the last 2 days)
Updating autoloads for directory /home_user/max/programme/gnus/lisp...
Generating autoloads for lisp/binhex.el...
No autoloads found in lisp/cus-load.el
No autoloads found in lisp/dgnushack.el
No autoloads found in lisp/dig.el
Generating autoloads for lisp/earcon.el...
No autoloads found in lisp/flow-fill.el
No autoloads found in lisp/format-spec.el
Generating autoloads for lisp/gnus-agent.el...
Unbalanced parentheses
xemacs exiting
.
make[1]: *** [gnus-load.elc] Error 255
make[1]: Leaving directory `/home_user/max/programme/gnus/lisp'
make: *** [lick] Error 2
[max@goofy gnus]$
System: redhat 7.0
xemacs 21.2.42
Max
--
when I find my code in tons of trouble,
friends and colleagues come to me,
speaking words of wisdom
"write in C"
next prev parent reply other threads:[~2001-02-12 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-11 1:52 NAGY Andras
2001-02-11 14:53 ` ShengHuo ZHU
2001-02-11 17:01 ` NAGY Andras
2001-02-12 17:44 ` Max Kliche [this message]
2001-02-12 20:02 ` ShengHuo ZHU
2001-02-13 9:44 ` Max Kliche
2001-02-13 15:23 ` ShengHuo ZHU
2001-07-04 12:43 Compilation error Stein A. Strømme
2001-07-04 13:34 ` Didier Verna
2001-07-04 13:41 ` Stein A. Strømme
2001-07-04 13:54 ` Didier Verna
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=m3d7cnzthz.fsf@kliche.org \
--to=max@kliche.org \
--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).