ninja is always recompiling everything · Issue #2703 · ninja-build/ninja · GitHub
//voltron/issues_fragments/issue_layout" data-turbo-transient="true" />
Skip to content
Search or jump to...
Search code, repositories, users, issues, pull requests...
-->
Search
Clear
Search syntax tips
Provide feedback
--><br>We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel
Submit feedback
Saved searches
Use saved searches to filter your results more quickly
-->
Name
Query
To see all available qualifiers, see our documentation.
Cancel
Create saved search
Sign in
//voltron/issues_fragments/issue_layout;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up
Appearance settings
Resetting focus
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
ninja-build
ninja
Public
Notifications<br>You must be signed in to change notification settings
Fork<br>1.8k
Star<br>13k
ninja is always recompiling everything #2703
New issue<br>Copy link
New issue<br>Copy link
Closed<br>Bug<br>#2764
Closed<br>ninja is always recompiling everything#2703<br>Bug<br>#2764
Copy link
Milestone<br>1.14.0
Description
bitbugprime<br>opened on Dec 28, 2025
Issue body actions
ninja version: 1.13.2
cmake version: 4.2.1
I'm not sure if it's related but I always get a "premature end of file; recovering" error from ninja when it runs. Annoyingly, ninja doesn't report the name of the offending file. CMake v4 bug?
In any case, if ninja runs the build to completion rerunning it recompiles everything it just built. I don't know how to debug this or what you need from me to reproduce it yourself.
Ninja 1.12.1 still gives the "premature end of file" warning, but doesn't exhibit the "always rebuild everything" behavior. Also, interestingly, it reports a different number for the total job size than 1.13.2 does. 1.13.2 thought there were about 1900 items left to build, which number doesn't change on a repeat build, while 1.12.1 reports about 3600 (and does properly decrease on a partial build).
Reactions are currently unavailable
Metadata<br>Metadata<br>Assignees
No one assigned
Labels
No labelsNo labels
Type
Bug
Fields<br>Give feedback
No fields configured for Bug.
Projects
No projects
Milestone
1.14.0No due date
Relationships
None yet
Development
No branches or pull requests
Issue actions
You can’t perform that action at this time.