E06264: dependency needs a newer compiler
What went wrong
A dependency named in your 'defines package' block ('deps' or 'devDeps') needs a newer EK9 compiler than the one running now. Its effective minimum compiler is either the 'minimumCompiler' Version literal its own package block declares, or - when it declares none - the compiler that packaged it (recorded as 'compiler=' in its '.package.properties'; a package built BEFORE this check existed carries neither, so it has no effective minimum and can never trigger this). The highest minimum over every dependency in the resolved set is compared against this compiler's own version at the point the set is chosen; a transitive dependency names the package that pulled it in. 'ek9 -c' reports this when it resolves dependencies and stops with exit code 17 - that includes a build whose 'ek9.lock' is stale for any reason, since a stale lock always re-resolves before this is reported. Only a door (the IDE, 'ek9_query_build_status') reads the lock's own 'minimum-compiler' line directly and reports it without resolving anything.
How to fix it
- Update EK9 to a version at least as new as the one named in the message.
- If you cannot update yet, install a version of the dependency that was built for this compiler (an older version, or one the publisher built against an older EK9) and change the version in 'deps'/'devDeps' to match.
- If you maintain the dependency yourself, lower its 'minimumCompiler' (or remove it) if the feature it needs is not actually required, or republish it once your own EK9 compiler is the one you want consumers to need.
Common causes
- A dependency published with a newer compiler than consumers have installed, falling back to its packaging compiler's version ('compiler=') because it declares no 'minimumCompiler' of its own
- A transitive dependency (pulled in by another) declaring a higher minimum than the direct dependency that named it
- NOT this: a package built BEFORE this check existed. It carries no 'compiler=' in its '.package.properties' at all, so it has no effective minimum and can never trigger this error
See also
- E06263: a dependency is not installed in the library
- E06260: a package property of the wrong shape, or unknown
- https://ek9.io/packaging.html
Examples
No compiled example of E06264 is held in the error catalogue yet; the explanation above is the rich message the compiler shows for it (ek9 -h E06264).
Found a problem?
If EK9 reported E06264 for a program you think is valid, or did not report it where it should have, use the compiler form with the smallest program that shows it. If this page is wrong or unclear, use the documentation form. Both are at github.com/ek9lang/ek9-issues.