Leiningen version < 2.4.3 trouble

[rogerallen]

I've updated my Mac to OS X Mavericks 10.9.4 and now I can't run shadertone past v0.2.2. I think this may be a 10.9 issue, not a 10.9.x issue, but I'm still figuring this out.

The error reported is:

Exception in thread "main" java.lang.UnsatisfiedLinkError: no lwjgl in java.library.path
    at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1886)
    at java.lang.Runtime.loadLibrary0(Runtime.java:849)
    at java.lang.System.loadLibrary(System.java:1088)
    at org.lwjgl.Sys$1.run(Sys.java:73)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.lwjgl.Sys.doLoadLibrary(Sys.java:66)
    at org.lwjgl.Sys.loadLibrary(Sys.java:95)
    at org.lwjgl.Sys.<clinit>(Sys.java:112)
    at org.lwjgl.opengl.Display.<clinit>(Display.java:135)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:190)
    at shadertone.shader$eval10112$loading__4910__auto____10113.invoke(shader.clj:1)
    at shadertone.shader$eval10112.invoke(shader.clj:1)
...

This tag uses the older release of lwjgl v2.9.0 instead of v2.9.1.

I've also updated Java & Lein, but I don't think that's it.
Leiningen 2.4.2 on Java 1.7.0_60 Java HotSpot(TM) 64-Bit Server VM

[rogerallen]

Maybe this is a Lein issue instead? Latest from github works on another Mac OS X 10.9.4 with
Leiningen 2.3.3 on Java 1.6.0_65 Java HotSpot(TM) 64-Bit Server VM

But, after lein upgrade to
Leiningen 2.4.2 on Java 1.6.0_65 Java HotSpot(TM) 64-Bit Server VM

I get:
Invalid memory access of location 0x1 rip=0x108d3266d
(and a crash reporter came up long after that)

[rogerallen]

Indeed, I believe this is the issue here: technomancy/leiningen#1607

(Created an hour ago. This is an odd bit of synchronicity with @lilinjn)

[rogerallen]

This will be resolved when leiningen 2.4.3 releases. Will keep this open until it is released.

It doesn't seem like there is any lein version safe from this issue. I'm not sure why it started being a problem recently.

[rogerallen]

Leiningen 2.4.3 resolves the issue. Closing