Hello, I also had tk as a sticking point in my last run of "upgrade outdated" (after selfupdate to 2.4.3). It came very near the end of updating everything so I succumbed to temptation and forced it with -f. I haven't noticed anything going terribly wrong yet, but "tk contents" does show the X11 header files including X.h in /opt/local/include/X11.
What should I be looking for that might indicate that it is causing problems and what is the specific procedure to remove/repair this? (I have read the previous messages in this thread but want to be certain I am not uninstalling or "nuking" anything beyond what might be absolutely necessary.) I have El Capitan 10.11.6. Thanks for any help. On Wed, Apr 18, 2018 at 4:08 AM pagani laurent via macports-users < macports-users@lists.macports.org> wrote: > Ryan, > > I removed explicit tk installation from the myport.txt list, uninstalled > tk and restarted restore_ports.tcl myport.txt and all went through nicely. > Tk has been reinstalled as requested from python ports as dependent port. > And in that case, it does not contain explicitly X.h and other such header > files as you can see in the new ”port contents tk” command return which I > attach to this mail but I also provide directly the difference between the > two (left side is the one from requested installation, left one from > indirect installation) : > > Macports>diff tk_contents.txt tk_contents_2.txt > 4,12d3 > < /opt/local/include/X11/X.h > < /opt/local/include/X11/Xatom.h > < /opt/local/include/X11/Xfuncproto.h > < /opt/local/include/X11/Xlib.h > < /opt/local/include/X11/Xutil.h > < /opt/local/include/X11/cursorfont.h > < /opt/local/include/X11/keysym.h > < /opt/local/include/X11/keysymdef.h > < /opt/local/include/X11/xbytes.h > 15,16d5 > < /opt/local/include/tkIntXlibDecls.h > < /opt/local/include/tkMacOSX.h > 18,19d6 > < /opt/local/lib/Tk.icns > < /opt/local/lib/Tk.tiff > > Hope this helps. > > L. > >
