This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-03
Channels
- # babashka (17)
- # beginners (166)
- # calva (97)
- # cider (4)
- # clara (2)
- # clj-kondo (46)
- # cljsrn (5)
- # clojure (334)
- # clojure-canada (1)
- # clojure-dev (144)
- # clojure-europe (14)
- # clojure-germany (5)
- # clojure-nl (10)
- # clojure-spec (1)
- # clojure-uk (46)
- # clojurescript (50)
- # conjure (1)
- # core-async (52)
- # core-typed (5)
- # cursive (3)
- # datomic (3)
- # emacs (11)
- # figwheel (16)
- # figwheel-main (9)
- # fulcro (29)
- # graalvm (19)
- # graphql (14)
- # helix (46)
- # hoplon (4)
- # hugsql (2)
- # jobs (2)
- # jobs-discuss (1)
- # juxt (15)
- # kaocha (6)
- # off-topic (9)
- # pedestal (7)
- # portkey (7)
- # re-frame (10)
- # reagent (29)
- # shadow-cljs (13)
- # spacemacs (70)
- # sql (13)
- # tools-deps (26)
- # xtdb (23)
The only thing stopping me from further exploration of using graalvm with clojure (I know the patch is coming with the resolution to lockable thing), is the inability for graalvm to resolve directories, e.g., for configuration files: https://github.com/oracle/graal/issues/1108
@dharrigan patch coming? the patch is already there: 1.10.2-alpha1. getResource should also work, but you have to configure it to include resources in the binary.
getResource might work, but for libraries that use a different mechanism, it might fail
I'm using (
. All of this stuff is included: https://github.com/borkdude/clj-kondo/tree/master/resources/clj_kondo/impl/cache/built_in/clj
Unprefixed locations or locations with the classpath: prefix target the Java classpath.
Hello. I was hoping to get some guidance (or at least maybe a fresh look) on an issue I am running into. I am using graalvm version 20.1.0.java11 and native image to create a binary using github actions. It is using the latest ubuntu image as a base and when I test the binary in the github action it does work as expected. The problem is when I download the binary and run it on my fedora box I am getting a SEGFAULT error. Anyone have any ideas on what could be causing this? Thanks!
@patrick.farwick CircleCI is known to not have this problem.
adding --static to the native-image build seemed to do the trick
mustve been an issue with glibc?
I have not checked out circleci but will eventually give it a go
@patrick.farwick Note that --static
is only supported for linux binaries and may give other problems.
I appreciate the heads up!