Document source revision and build provenance of Windows libtommath.dll in Tcl/Tk 9.0.4
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Documentation
Could the source release/commit and build provenance be documented for the Windows x64 libtommath.dll supplied with CPython's Tcl/Tk 9.0.4 dependency bundle?
Public artifact references:
- cpython-bin-deps: tcltk-9.0.4.0/amd64/bin/libtommath.dll
- cpython-source-deps: tcl-9.0.4.0/libtommath/win64
- The corresponding Tcl Windows makefile
The DLL in both repositories has Git blob ID 856af88d7e51af58d705d9b187a0b151880bafee and size 81,408 bytes. It has no file/product version resource. The dynamic x64 makefile copies that prebuilt DLL instead of compiling the adjacent LibTomMath sources, so the neighboring source changelog does not by itself establish the DLL's source revision.
A pointer to the exact upstream release/commit, build recipe/toolchain, and applicable license/notice would make component attribution and advisory-version matching possible without guessing. If this information already exists, could it be linked alongside the binary dependency records?
This is a provenance/documentation request, not a report of a confirmed vulnerability. I am filing here because the binary-dependency repository has issues disabled.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the referenced tcl-9.0.4.0/win/makefile.vc and the amd64 libtommath.dll and win64 source paths, then trace how the dynamic x64 build handles the prebuilt DLL. Done means linking the exact upstream source release or commit, documenting the build recipe and toolchain, and recording the applicable license or notice alongside the binary dependency records.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100