Questions about unicodedata in python 2.6.2

[Weidong]

On Jul 28, 12:37 pm, Christian Heimes <li... at cheimes.de> wrote:
> 'make install' shouldn't compile any libraries if you run 'make' prior
> to 'make install'. I suggest you start again with a clean build tree of
> Python 2.6.2.
>
> Christian

You are perfectly right.  I started everything again after a "make
distclean".  This time I configured it as follows:

./configure --enable-unicode=ucs2 --enable-shared

to make things explicit, although I guess that the defaults would be
the same even when "--enable-unicode=ucs2 --enable-shared" are not
specified (in my case where ucs4 is not available).  The Makefile
generated then contains meaningful flags in RUNSHARED which was absent
before.

With this configuration, "make" was fine, except it "only" has the
following problems:

Failed to find the necessary bits to build these modules:
bsddb185           gdbm               sunaudiodev
To find the necessary bits, look in setup.py in detect_modules() for
the module's name.

That was not surprised because I did not have those available on my
machine.

The unicodedata.so was also created in the "make" process, and "make
install" showed no problem.

"make test" showed the following problems:

test_aepack
test_aepack skipped -- No module named aepack
test_al
test_al skipped -- No module named al
test_anydbm
Exception bsddb.db.DBRunRecoveryError: DBRunRecoveryError(-30974,
'DB_RUNRECOVERY: Fatal error, run database recovery -- PANIC: fatal
region error detected; run recovery') in  ignored

I guess this is caused by the missing bsddb185.  However, the problem
is, "make test" seemed to be hanging at that fatal error.

Do you know how critical are those failed tests?

Thanks for your help!

- Weidong