Gnus development mailing list
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: Katsumi Yamaoka <yamaoka@jpl.org>, ding@gnus.org
Subject: Re: Wrong type argument: stringp when Generating cus-load.el
Date: Thu, 07 Nov 2002 13:04:33 -0600	[thread overview]
Message-ID: <87adklurpa.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <878z059pxv.fsf@pod.hq.spin.de> (Andi Hechtbauer's message of "Thu, 07 Nov 2002 19:48:12 +0100")

Andi Hechtbauer <anti@spin.de> writes:

> Hi,
>
> [CVS gnus wouldn't compile with cus-dep.el(c) in emacs21(-el) 21.2-5]
>
>     Andi> I just installed the .el files.  Hopefully this is a more
>     Andi> interessting Backtrace now: [...]
>
>     Katsumi> I see.  That file is the thing of Emacs 21.3.50, and,
>     Katsumi> moreover, there is a bug.
>
> Hm, if that is true, debian is to blame.  Or me, living on the
> unstable edge ;-)

Well it's actually debian including a patch that's also been included
upstream.  It was a patch to fix things so that emacs built
--with-x=yes and emacs --with-x=no wouldn't have spurious differences
in some of its files.

I wrote the patch initially and RMS included it upstream, but I had
the same build problem here when I tried to compile the latest gnus.
I haven't have time to fully investigate, but what I did find out was
that the problem can be fixed by removing the "members sort".  The
all-subdirs sort doesn't seem to cause trouble.

> Rob Browning <rlb@defaultvalue.org> (Cc set) packaged this file with
> emacs21-el Version 21.2-5 -- the file itself has no hint about
> version.  And changelog.Debian.gz isn't suggesting this, either.

If you look in /usr/share/doc/emacsen21-common/README.Debian.gz, it
mentions the relevant patch near the end.  You can "apt-get source
emacs21" and look in debian/patch to see the actual diff, or just grab
the debian diff file.

> ,----
> | 2002-09-19  Richard M. Stallman  <rms@gnu.org>
> | 
> | 	* cus-dep.el (custom-make-dependencies): Fix previous change.
> | 
> | 2002-09-18  Richard M. Stallman  <rms@gnu.org>
> | [...]
> | 	* cus-dep.el (custom-make-dependencies): Sort MEMBERS before use.
> `----

I'll need to see what RMS changed back and fix that here too.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu



  reply	other threads:[~2002-11-07 19:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-07  2:13 Andi Hechtbauer
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 [this message]
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=87adklurpa.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=ding@gnus.org \
    --cc=yamaoka@jpl.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).