Output from failed platform_triplet.c compilation is not logged
Open
Nobody has claimed this yet.
build
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
Bug report
Bug description:
In #117886, building platform_triplet.c was failing, but the only output in config.log was:
configure:6892: checking for the platform triplet based on compiler characteristics
configure:6900: result: none
At least in the case of failure, the compile command and output should be logged.
CPython versions tested on:
3.13
Operating systems tested on:
macOS
Linked PRs
- gh-134905
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 platform_triplet.c compilation and the configure entry point described in the report. Compare the failed build's command and output with what is currently written to config.log. Done means a failed compilation logs both the compile command and its output; check linked PR gh-134905 for existing work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100