https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286298
--- Comment #1 from Chad Jacob Milios <mil...@ccsys.com> --- Created attachment 260621 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=260621&action=edit patch-foo for $FILESDIR merely adding "internal/" to that line and the next worked to get py312-tkinter-3.12.10_10 building and packaging. i did not conventionalize this patch regarding PYTHON_REL nor did i test that it doesnt break 39-311. i also didnt figure out why it breaks and why that works; the two cc invocations are practically identical and the referenced headers are in the same spot 3.11 -> 3.12. ===> Building for py311-tkinter-3.11.12_10 ...snip... creating build/temp.freebsd-13.5-RELEASE-p1-amd64-cpython-311 cc -Wsign-compare -Wunreachable-code -DNDEBUG -O2 -pipe -march=opteron-sse3 -fstack-protector-strong -fno-strict-aliasing -O2 -pipe -march=opteron-sse3 -fstack-protector-strong -fno-strict-aliasing -fPIC -DWITH_APPINIT=1 -I/usr/local/include -I/usr/local/include/tcl8.6 -I/usr/local/include/tk8.6 -I/usr/local/include -I/usr/local/include/python3.11 -c _tkinter.c -o build/temp.freebsd-13.5-RELEASE-p1-amd64-cpython-311/_tkinter.o ...(carries on)... -o build/temp.freebsd-13.5-RELEASE-p1-amd64-cpython-311/tkappinit.o .............. GreatSuccess[TM] ===> Building for py312-tkinter-3.12.10_10 ...... creating build/temp.freebsd-13.5-RELEASE-p1-amd64-cpython-312 cc -fno-strict-overflow -Wsign-compare -Wunreachable-code -DNDEBUG -O2 -pipe -march=opteron-sse3 -fstack-protector-strong -fno-strict-aliasing -O2 -pipe -march=opteron-sse3 -fstack-protector-strong -fno-strict-aliasing -fPIC -DWITH_APPINIT=1 -I/usr/local/include -I/usr/local/include/tcl8.6 -I/usr/local/include/tk8.6 -I/usr/local/include -I/usr/local/include/python3.12 -c _tkinter.c -o build/temp.freebsd-13.5-RELEASE-p1-amd64-cpython-312/_tkinter.o _tkinter.c:35:10: fatal error: 'pycore_long.h' file not found note: upon my initial run in to this problem there were no 3.11 python or packages installed on the system. -- You are receiving this mail because: You are the assignee for the bug.
