Discuss GraalVM related topics. Use clojure 1.10.2 or newer for all new projects. Contribute to and GraalVM slack:
Gerald T 2020-07-21T04:34:32.084400Z

I'm getting a weird issue when compiling a very mimimal project that has dependencies on [ "0.3.2"] and [com.taoensso/timbre "4.10.0"] with GraalVM native-image. Project is using [org.clojure/clojure "1.10.2-alpha1"] and compiled with .

native-image --no-fallback \
--initialize-at-build-time --allow-incomplete-classpath --report-unsupported-elements-at-runtime \
-jar ./target/test2-0.1.0-SNAPSHOT-standalone.jar
native-image can be compiled if either timbre or java-time is left out. It only occurs when a specific call to timbre/log is called:
(ns test2.core
  (:require [taoensso.timbre :as log]
            [java-time :as t])

(set! *warn-on-reflection* true)

(defn -main [& args]
  (println "testing")
  (log/info "testing")    ;; no error is triggered
  (println (t/local-date-time))    ;; no error is triggered
  (log/info "local-date" (t/local-date-time))) ;; this triggers the compile error
Build on Server(pid: 51885, port: 54536)
[test2-0.1.0-SNAPSHOT-standalone:51885]    classlist:  11,272.74 ms,  2.23 GB
[test2-0.1.0-SNAPSHOT-standalone:51885]        (cap):   7,855.84 ms,  2.23 GB
[test2-0.1.0-SNAPSHOT-standalone:51885]        setup:  12,344.01 ms,  2.23 GB
[test2-0.1.0-SNAPSHOT-standalone:51885]     (clinit):   5,899.36 ms,  2.73 GB
[test2-0.1.0-SNAPSHOT-standalone:51885]   (typeflow): 366,268.13 ms,  2.73 GB
[test2-0.1.0-SNAPSHOT-standalone:51885]    (objects): 103,610.17 ms,  2.73 GB
[test2-0.1.0-SNAPSHOT-standalone:51885]   (features):   6,134.04 ms,  2.73 GB
[test2-0.1.0-SNAPSHOT-standalone:51885]     analysis: 501,193.69 ms,  2.73 GB
[test2-0.1.0-SNAPSHOT-standalone:51885]     universe:   9,507.73 ms,  2.74 GB
[test2-0.1.0-SNAPSHOT-standalone:51885]      (parse):  48,237.15 ms,  2.75 GB
[test2-0.1.0-SNAPSHOT-standalone:51885]     (inline):  47,334.52 ms,  2.85 GB
[test2-0.1.0-SNAPSHOT-standalone:51885]    (compile): 185,888.11 ms,  2.45 GB
[test2-0.1.0-SNAPSHOT-standalone:51885]      compile: 298,379.85 ms,  2.45 GB
[test2-0.1.0-SNAPSHOT-standalone:51885]        image:  18,446.36 ms,  2.50 GB
Fatal$HostedError:$HostedError: java_time.amount$days.invokeStatic(Object): has no code address offset set.
	at java.base/java.util.concurrent.ForkJoinTask$AdaptedRunnableAction.exec(
	at java.base/java.util.concurrent.ForkJoinTask.doExec(
	at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(
	at java.base/java.util.concurrent.ForkJoinPool.scan(
	at java.base/java.util.concurrent.ForkJoinPool.runWorker(
	at java.base/
Caused by:$HostedError: java_time.amount$days.invokeStatic(Object): has no code address offset set.
	... 7 more
Error: Image build request failed with exit status 1

Gerald T 2020-07-21T04:39:32.084900Z

OpenJDK Runtime Environment GraalVM CE 20.1.0 (build 11.0.7+10-jvmci-20.1-b02)
OpenJDK 64-Bit Server VM GraalVM CE 20.1.0 (build 11.0.7+10-jvmci-20.1-b02, mixed mode, sharing)

borkdude 2020-07-21T06:48:34.086500Z

@totoyok285 Could be a GraalVM bug. You can make a repro repository with clear build instructions and make an issue over there .