usr/local/lib/python2.6? What is the consequence if I do not put them
on the embedded system?
Is there a good way to directly make an installation "package" (or
tarball) of python 2.6.2 from the build result?
Any advice on configuration to make the results smaller will be
greatly
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
--
http://mail.python.org/mailman/listinfo/python-list
ignore that error. In the end, I still did not see unicodedata.so in
the build result. It seems that the Makefile did not even try to
build unicodedata.so.
Maybe something went wrong in my configuration?
- Weidong
--
http://mail.python.org/mailman/listinfo/python-list
On Jul 28, 9:54 am, Weidong wrote:
> I am trying to build python 2.6.2 from the source by following the
> instructions in README that comes with the source. The configure and
> make steps are fine, but there is an error in "make install" step.
> This "make install"
2? If it is needed, why
it is commented out by default in Modules/Setup.dist? If it is not
needed, why "make install" attempts to use it in compiling the
libraries? Why those libraries are not designed to be compiled in the
make step, but in the install step?
Thanks for your help!
- Weidong
--
http://mail.python.org/mailman/listinfo/python-list
