Re: wrong-type-argument charsetp unbound error in emacs-unicode-2 current

[James Cloos <cloos@jhcloos.com>]

>>>>> "Bob" == Bob Halley <halley@play-bow.org> writes:

Bob> Up until a few days ago, I had no problem with running the head
Bob> of the emacs-unicode-2 branch, but it is now failing.

Bob> If I start emacs and then kill some text, e.g. something simple
Bob> like "foo^A^K" in *scratch*, then I get a (wrong-type-argument
Bob> charsetp unbound) error.  Emacs usually doesn't survive long
Bob> after reporting that error either, typically dying with SIGSEGV
Bob> after a few additional editing operations.

I just gave it a try with a compile that is just a couple of hours
older than your post, and did not see the SEGV.

I use gentoo's ebuild for 23.0.0, and end up with this configure line:

./configure --prefix=/usr --host=i686-pc-linux-gnu \
 --mandir=/usr/share/man --infodir=/usr/share/info \
 --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib \
 --enable-debug --program-suffix=.emacs-23.0.0 --without-carbon \
 --with-x --with-xpm --with-toolkit-scroll-bars --enable-font-backend \
 --with-freetype --with-xft --with-jpeg --with-tiff --with-gif \
 --with-png --with-x-toolkit=athena --build=i686-pc-linux-gnu

Which toolkit do you use?  I've noticed that using gtk (as emacs'
toolkit) often leads to more bugs than the alternatives.....

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 0xED7DAEA6