ryandesign at macports.org
Thu Apr 19 04:42:28 UTC 2018
Thanks. I think this problem was introduced by a presumably unintentional part of this commit:
I think that needs to be reverted, and the tk port's revision increased to ensure any incorrect builds out there get fixed.
On Apr 18, 2018, at 04:08, pagani laurent wrote:
> 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
> < /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
> < /opt/local/include/tkIntXlibDecls.h
> < /opt/local/include/tkMacOSX.h
> < /opt/local/lib/Tk.icns
> < /opt/local/lib/Tk.tiff
> Hope this helps.
More information about the macports-users