Sorin Schwimmer wrote:
> /usr/local/lib is in /etc/ld.so.conf. The files are real. However,
> creating symlinks in /usr/lib targeting the libraries in /usr/local/lib,
> then recompiling, solved the tkinter problem. So, the conclusion is that
> only /usr/lib is consulted for the tcl/tk libraries.
Hello again,
/usr/local/lib is in /etc/ld.so.conf. The files are real. However,
creating symlinks in /usr/lib targeting the libraries in /usr/local/lib,
then recompiling, solved the tkinter problem. So, the conclusion is that
only /usr/lib is consulted for the tcl/tk libraries.
multiprocessing -
Sorin Schwimmer wrote:
>
> Thanks for the pointers.
>
> Here are some answers:
>
> > Ok, so DBM wasn't built because it couldn't find the external symbol
> > 'dbm_firstkey'. I have no idea off the top of my head why that would
> > happen, but I don't think you really care at the moment since y
Thanks for the pointers.
Here are some answers:
> Ok, so DBM wasn't built because it couldn't find the external symbol
> 'dbm_firstkey'. I have no idea off the top of my head why that would
> happen, but I don't think you really care at the moment since you are
> trying to get tkinter working.
Sorin Schwimmer wrote:
>
> I wanted to replace my old Python 2.4 and tcl/tk 8.4 with tcl/tk 8.5.6 and
> Python 2.6, mainly so that I can enjoy ttk. tcl/tk was installed from sources
> without any problem, I started a wish and worked.
>
> Now, for the Python, here are all the issues signaled by
I wanted to replace my old Python 2.4 and tcl/tk 8.4 with tcl/tk 8.5.6 and
Python 2.6, mainly so that I can enjoy ttk. tcl/tk was installed from sources
without any problem, I started a wish and worked.
Now, for the Python, here are all the issues signaled by make test:
running build
running b
Sorin Schwimmer wrote:
>
> > Run 'make test' instead of running them one by one.
>
> I did it *before* going one by one. I then tried individual tests in hope of
> getting hints of what to look for. Actualy, for the first three tests, the
> "make test" script commented that it is unusual for t
> Run 'make test' instead of running them one by one.
I did it *before* going one by one. I then tried individual tests in hope of
getting hints of what to look for. Actualy, for the first three tests, the
"make test" script commented that it is unusual for them to fail on my platform
(linux2)