You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Tkinter modules built successfully but removed because they could not be imported #69434
bpo-31817: Compilation Error with Python 3.6.1/3.6.3 with Tkinter
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2020-05-29.10:26:45.154>created_at=<Date2015-09-27.14:09:15.953>labels= ['build', 'expert-tkinter']
title='Tkinter modules built successfully but removed because they could not be imported'updated_at=<Date2020-05-29.10:26:45.153>user='https://bugs.python.org/abrantesasf'
It looks like this is the same issue that has been discussed in later bpo-31817. Since there has been more discussion there, let's close this as a duplicate of that one.
Activity
abrantesasf commentedon Sep 27, 2015
I'm trying to compile Python 3.5 on a CentOS 7.1, with TCL 8.6.4, but make always give me the following message:
*** WARNING: renaming "_tkinter" since importing it failed: build/lib.linux-x86_64-3.5/_tkinter.cpython-35m-x86_64-linux-gnu.so: undefined symbol: Tcl_GetCharLength
Following modules built successfully but were removed because they could not be imported:
_tkinter
The configure command was the following (both, Tcl and Tk are installed under /usr/local/lib/tcl8.6.4):
I could not found a solution for this issue, and I do not know if this is a bug.
serhiy-storchaka commentedon Sep 27, 2015
Do you have other Tcl versions in 8.6 branch installed? Try to set
export LD_LIBRARY_PATH=/usr/local/lib/tcl8.6.4/lib
abrantesasf commentedon Sep 27, 2015
No, I do not have any other Tcl version on my system, and my LD_LIBRARY_PATH alredy points to Tcl directory.
The problem with tkinter persist even if I explicity export LD_LIBRARY_PATH before the compilation.
Any other ideas?
Thanks!
abrantesasf commentedon Sep 28, 2015
I tried with LD_RUN_PATH, but the same compile error still there.
ned-deily commentedon May 29, 2020
It looks like this is the same issue that has been discussed in later bpo-31817. Since there has been more discussion there, let's close this as a duplicate of that one.