From: Oystein Viggen <oysteivi@tihlde.org>
Subject: compile error with newest CVS on xemacs
Date: Thu, 01 May 2003 11:47:51 +0200 [thread overview]
Message-ID: <03llxrvvzs.fsf@msgid.viggen.net> (raw)
Hi
(sorry if this ends up being posted twice.. I still can't see my first
try at posting.)
I got the following compile error with CVS as of 10:56 AM Norwegian time
(CET):
---begin compile output---
: oysteivi@colargol:~/cvs/gnus; make
cd lisp && make EMACS="xemacs" lispdir="/usr/share/xemacs/site-packages/lisp/gnus" all
make[1]: Entering directory `/home/xdrift/oysteivi/cvs/gnus/lisp'
rm -f *.elc gnus-load.el
URLDIR=/usr/share/xemacs21/packages/lisp/w3/ W3DIR=/usr/share/xemacs21/packages/lisp/w3/ lispdir=/usr/share/xemacs/site-packages/lisp/gnus srcdir=. xemacs -batch -no-autoloads -l ./dgnushack.el -f dgnushack-make-cus-load .
Loading cus-dep...
Processing /home/xdrift/oysteivi/cvs/gnus/lisp
(No changes need to be written)
URLDIR=/usr/share/xemacs21/packages/lisp/w3/ W3DIR=/usr/share/xemacs21/packages/lisp/w3/ lispdir=/usr/share/xemacs/site-packages/lisp/gnus srcdir=. xemacs -batch -no-autoloads -l ./dgnushack.el -f dgnushack-make-auto-load .
Symbol's function definition is void: defadvice
xemacs exiting
.
make[1]: *** [gnus-load.el] Error 255
make[1]: Leaving directory `/home/xdrift/oysteivi/cvs/gnus/lisp'
make: *** [lick] Error 2
---end compile output---
This is with the standard xemacs-mule from Debian Woody, using
./configure --with-xemacs. Compiling worked a few days ago. Running
non-byte-compiled also seems to work. (I'm too stupid to back up my
working snapshot before cvs update -Pd.. :)
Øystein
--
This message was brought to you by the letter ß and the number e.
next reply other threads:[~2003-05-01 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 9:47 Oystein Viggen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-01 9:04 Oystein Viggen
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=03llxrvvzs.fsf@msgid.viggen.net \
--to=oysteivi@tihlde.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).