Skip to content

Accept dev versions of coq, coq-compcert and coq-flocq in coq-vst.opam#860

Closed
JasonGross wants to merge 3 commits into
PrincetonUniversity:masterfrom
JasonGross:master+rocq-dev
Closed

Accept dev versions of coq, coq-compcert and coq-flocq in coq-vst.opam#860
JasonGross wants to merge 3 commits into
PrincetonUniversity:masterfrom
JasonGross:master+rocq-dev

Conversation

@JasonGross

Copy link
Copy Markdown
Contributor

Allows installing a pin to this branch on a switch tracking Rocq master

JasonGross and others added 3 commits July 15, 2026 20:17
Allows installing on a switch tracking Rocq master (e.g. pinned
rocq-core dev builds); release constraints are unchanged.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019ttctspSoVoquHLQtbPVZw
The main coqdep invocation piped through grep with `|| true`, so a
coqdep that dies partway (e.g. killed under memory pressure) silently
leaves a truncated .depend; the `.depend depend:` rule has no
prerequisites, so later builds reuse the poisoned file and parallel
make compiles files before their dependencies exist ("Unable to locate
library ..." errors).  Write to a temporary file, fail the build if
coqdep fails, keep the warning filtering, and move the file in place
only on success.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019ttctspSoVoquHLQtbPVZw
coqdep in current Rocq dev leaks one file descriptor per located
warning (fix proposed as rocq-prover/rocq#22278); over this tree's
thousands of module-not-found warnings it dies with "Too many open
files" under the common 1024 soft limit.  Raise the soft limit to the
hard limit for the coqdep invocation as a harmless workaround for
affected Rocq versions.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019ttctspSoVoquHLQtbPVZw
@JasonGross JasonGross closed this Jul 16, 2026
@andrew-appel

Copy link
Copy Markdown
Collaborator

@JasonGross can you explain further? How is this branch going to track the master branch? Will you have to fastforward from time to time? And why need a P.R. instead of just a fork branch?

@JasonGross

JasonGross commented Jul 16, 2026

Copy link
Copy Markdown
Contributor Author

Moving discussion to #861 which is not capturing other commits. (I accidentally opened the PR from my branch combining a handful of fixes, rather than separating them out.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants