From: Andi Hechtbauer <anti@spin.de>
Cc: ding@gnus.org
Subject: Re: Problems building CVS source.
Date: Sun, 24 Nov 2002 01:43:21 +0100 [thread overview]
Message-ID: <87vg2nu79y.fsf@pod.hq.spin.de> (raw)
In-Reply-To: <87n0o14i0j.fsf@paranoia.ahnberg.pp.se> (Mattias Ahnberg's message of "Fri, 22 Nov 2002 18:43:40 +0100")
Hi,
>>>>> Mattias Ahnberg writes:
MA> I've been downloading the last three days source to try to get
MA> this working, but I can't figure it out and the problem
MA> [...]
MA> Generating cus-load.el... Wrong type argument: stringp,
MA> (mm-inline-text-html-with-w3m-keymap custom-variable)
I had this bite me some weeks ago. The problem was Debian including a
different (too recent) cus-dep.el. And Katsumi Yamaoka kindly pointed
us to the very spot:
>>>>> In <yotlk7jpm3jz.fsf@jpl.org>
>>>>> Katsumi Yamaoka <yamaoka@jpl.org> wrote:
>> --- cus-dep.el-20020917 2001-07-16 12:22:58 +0000
>> +++ cus-dep.el-20020918 2002-09-18 16:01:21 +0000
>> @@ -86,6 +86,8 @@
>> (let ((members (get symbol 'custom-group))
>> item where found)
>> (when members
>> + ;; So x and no-x builds won't differ.
>> + (setq members (sort (copy-sequence members) 'string<))
>> (while members
>> (setq item (car (car members))
>> members (cdr members)
Katsumi> If Debian contains the 20020918 version of cus-dep.el, it
Katsumi> seems to be fixed by simply applying the above patch
Katsumi> reverse.
This has been confirmed to solve the Problem.
bye,
Andi
prev parent reply other threads:[~2002-11-24 0:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-22 17:43 Mattias Ahnberg
2002-11-23 16:06 ` Kai Großjohann
2002-11-24 11:01 ` Mattias Ahnberg
2002-11-24 14:09 ` Kai Großjohann
[not found] ` <87d6ovkz9s.fsf@paranoia.ahnberg.pp.se>
[not found] ` <84of8f2non.fsf@lucy.cs.uni-dortmund.de>
[not found] ` <87ptsuki0e.fsf@paranoia.ahnberg.pp.se>
[not found] ` <84y97iyiw7.fsf@lucy.cs.uni-dortmund.de>
2002-11-24 18:27 ` Mattias Ahnberg
2002-11-25 7:40 ` Kai Großjohann
2002-11-24 0:43 ` Andi Hechtbauer [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=87vg2nu79y.fsf@pod.hq.spin.de \
--to=anti@spin.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).