Gnus development mailing list
 help / color / mirror / Atom feed
From: Andi Hechtbauer <anti@spin.de>
Subject: Wrong type argument: stringp when Generating cus-load.el
Date: Thu, 07 Nov 2002 03:13:34 +0100	[thread overview]
Message-ID: <m3n0omi0tt.fsf@hic.hq.spin.de> (raw)

Hi,

from time to time I do a clean compile of CVS gnus, as I usually just
"make some".  But this morning (and up til now, using the freshest CVS
gnus) the procedure "make distclean; ./configure; make" broke at
making gnus-load.el:

 $ make
 cd lisp && make EMACS="emacs" lispdir="/usr/share/emacs/site-lisp" all
 make[1]: Entering directory `/home/anti/lib/emacs/pgnus/lisp'
 rm -f *.elc gnus-load.el
 URLDIR=no W3DIR=no lispdir=/usr/share/emacs/site-lisp srcdir=. emacs -batch -q -no-site-file -l ./dgnushack.el -f dgnushack-make-cus-load .
 Loading cus-dep...
 Directory .
 Generating cus-load.el...
 Wrong type argument: stringp, (mm-inline-text-html-with-w3m-keymap custom-variable)
 make[1]: *** [gnus-load.el] Error 255
 make[1]: Leaving directory `/home/anti/lib/emacs/pgnus/lisp'
 make: *** [lick] Error 2

This is after I configured away url and w3, having them activated
makes no difference.

Is this obvious to one of you?  Has anyone seen the same thing and can
shed some light on a lisp-dummy?

Thanks for looking,

Andi



             reply	other threads:[~2002-11-07  2:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-07  2:13 Andi Hechtbauer [this message]
2002-11-07  4:18 ` Katsumi Yamaoka
2002-11-07  8:14   ` Manoj Srivastava
2002-11-07  9:07     ` Katsumi Yamaoka
2002-11-07 11:59       ` Andi Hechtbauer
2002-11-07 12:14         ` Katsumi Yamaoka
2002-11-07 12:52           ` Andi Hechtbauer
2002-11-07 14:46             ` Katsumi Yamaoka
2002-11-07 18:48               ` Andi Hechtbauer
2002-11-07 19:04                 ` Rob Browning
2002-11-07 22:13                   ` Katsumi Yamaoka
2002-11-07 22:24                     ` Katsumi Yamaoka
2002-11-08  2:02                       ` Manoj Srivastava

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=m3n0omi0tt.fsf@hic.hq.spin.de \
    --to=anti@spin.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).