| Summary: | =dev-lang/python-2.7.6 - *** WARNING: renaming "_tkinter" since importing it failed: libtk8.6.so: cannot open shared object file: No such file or directory | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jason Mours <jason.mours> |
| Component: | [OLD] Development | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | mgorny |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
build.log
emerge-info |
||
|
Description
Jason Mours
2014-02-13 18:48:34 UTC
Created attachment 370334 [details]
build.log
Created attachment 370336 [details]
emerge-info
I'm having similar issues with dev-lang/python-3.3.3 building _tkinter but it does not post missing modules cited in dev-lang/python-2.7.6... So this maybe my bug, was it safe to roll back tickle and toolkit? building '_tkinter' extension gcc -pthread -fPIC -fno-strict-aliasing -march=native -mtune=amdfam10 -Os -pipe -ggdb -fwrapv -DNDEBUG -DWITH_APPINIT=1 -DWITH_BLT=1 -I/usr/X11/include -I. -I/var/tmp/portage/dev-lang/python-2.7.6/work/Python-2.7.6/Include -I/var/tmp/portage/dev-lang/python-2.7.6/work/x86_64-pc-linux-gnu -c /var/tmp/portage/dev-lang/python-2.7.6/work/Python-2.7.6/Modules/_tkinter.c -o build/temp.linux-x86_64-2.7/var/tmp/portage/dev-lang/python-2.7.6/work/Python-2.7.6/Modules/_tkinter.o gcc -pthread -fPIC -fno-strict-aliasing -march=native -mtune=amdfam10 -Os -pipe -ggdb -fwrapv -DNDEBUG -DWITH_APPINIT=1 -DWITH_BLT=1 -I/usr/X11/include -I. -I/var/tmp/portage/dev-lang/python-2.7.6/work/Python-2.7.6/Include -I/var/tmp/portage/dev-lang/python-2.7.6/work/x86_64-pc-linux-gnu -c /var/tmp/portage/dev-lang/python-2.7.6/work/Python-2.7.6/Modules/tkappinit.c -o build/temp.linux-x86_64-2.7/var/tmp/portage/dev-lang/python-2.7.6/work/Python-2.7.6/Modules/tkappinit.o gcc -pthread -shared -Wl,-O1 -Wl,--as-needed -L. -Wl,-O1 -Wl,--as-needed -L. -fno-strict-aliasing -march=native -mtune=amdfam10 -Os -pipe -ggdb -fwrapv -DNDEBUG -I. -IInclude -I/var/tmp/portage/dev-lang/python-2.7.6/work/Python-2.7.6/Include build/temp.linux-x86_64-2.7/var/tmp/portage/dev-lang/python-2.7.6/work/Python-2.7.6/Modules/_tkinter.o build/temp.linux-x86_64-2.7/var/tmp/portage/dev-lang/python-2.7.6/work/Python-2.7.6/Modules/tkappinit.o -L/usr/X11/lib -L. -lBLT -ltk8.5 -ltcl8.5 -lX11 -lpython2.7 -o build/lib.linux-x86_64-2.7/_tkinter.so *** WARNING: renaming "_tkinter" since importing it failed: libtk8.6.so: cannot open shared object file: No such file or directory It references both libtk8.6.so and -ltk8.5 - which would you like to have? (In reply to Jeroen Roovers from comment #4) > building '_tkinter' extension > gcc -pthread -fPIC -fno-strict-aliasing -march=native -mtune=amdfam10 -Os > -pipe -ggdb -fwrapv -DNDEBUG -DWITH_APPINIT=1 -DWITH_BLT=1 > -I/usr/X11/include -I. > -I/var/tmp/portage/dev-lang/python-2.7.6/work/Python-2.7.6/Include > -I/var/tmp/portage/dev-lang/python-2.7.6/work/x86_64-pc-linux-gnu -c > /var/tmp/portage/dev-lang/python-2.7.6/work/Python-2.7.6/Modules/_tkinter.c > -o > build/temp.linux-x86_64-2.7/var/tmp/portage/dev-lang/python-2.7.6/work/ > Python-2.7.6/Modules/_tkinter.o > gcc -pthread -fPIC -fno-strict-aliasing -march=native -mtune=amdfam10 -Os > -pipe -ggdb -fwrapv -DNDEBUG -DWITH_APPINIT=1 -DWITH_BLT=1 > -I/usr/X11/include -I. > -I/var/tmp/portage/dev-lang/python-2.7.6/work/Python-2.7.6/Include > -I/var/tmp/portage/dev-lang/python-2.7.6/work/x86_64-pc-linux-gnu -c > /var/tmp/portage/dev-lang/python-2.7.6/work/Python-2.7.6/Modules/tkappinit.c > -o > build/temp.linux-x86_64-2.7/var/tmp/portage/dev-lang/python-2.7.6/work/ > Python-2.7.6/Modules/tkappinit.o > gcc -pthread -shared -Wl,-O1 -Wl,--as-needed -L. -Wl,-O1 -Wl,--as-needed -L. > -fno-strict-aliasing -march=native -mtune=amdfam10 -Os -pipe -ggdb -fwrapv > -DNDEBUG -I. -IInclude > -I/var/tmp/portage/dev-lang/python-2.7.6/work/Python-2.7.6/Include > build/temp.linux-x86_64-2.7/var/tmp/portage/dev-lang/python-2.7.6/work/ > Python-2.7.6/Modules/_tkinter.o > build/temp.linux-x86_64-2.7/var/tmp/portage/dev-lang/python-2.7.6/work/ > Python-2.7.6/Modules/tkappinit.o -L/usr/X11/lib -L. -lBLT -ltk8.5 -ltcl8.5 > -lX11 -lpython2.7 -o build/lib.linux-x86_64-2.7/_tkinter.so > *** WARNING: renaming "_tkinter" since importing it failed: libtk8.6.so: > cannot open shared object file: No such file or directory > > It references both libtk8.6.so and -ltk8.5 - which would you like to have? If I get to have a choice in the matter, -ltk8.5 seems like the way to go. With ruby not toolkiting proper with 8.6, I suppose I'll mask tcl/tk-8.6 and wait for tickle math to mature. I'll submit my python-3.3.3 bug as well. *** Bug 501336 has been marked as a duplicate of this bug. *** I can't reproduce here. Make sure you have removed both /usr/lib64/libtcl8.6.so and /usr/lib64/libtk8.6.so after downgrading to tcl-8.5 and tk-8.5. Portage will keep them installed if you have preserve-libs enabled. (In reply to Mike Gilbert from comment #7) > I can't reproduce here. > > Make sure you have removed both /usr/lib64/libtcl8.6.so and > /usr/lib64/libtk8.6.so after downgrading to tcl-8.5 and tk-8.5. Portage will > keep them installed if you have preserve-libs enabled. Neither file is on this machine, and /usr/lib64/libtk.so & /usr/lib64/libtcl.so are pointing to 8.5 Sorry to do this, but I can't see where tk8.6 is coming from. (In reply to Mike Gilbert from comment #9) > Sorry to do this, but I can't see where tk8.6 is coming from. It's probably legacy from when TCL/tk was multislot. Some sed statement of sorts, but I can't sed properly. Oh well. I'm still getting errors with dev-lang/python-3.3.4, which was no surprise. But I was wondering if the problem was with old legacy tickle/toolkit multi-slotting. It doesn't look like it was pulled out of python all the way. Could this be passed along? I'd rather see multislot come back to tcl/tk, but either way this could generate (be generating) more anomalies thru out. No action for 4 years. I don't think we can do or figure out more here. |