Clojurians Log v2

@carkh i cloned the portable repos to a windows 10 pro machine, ran script\build.cmd, then added the out\clojure-cli directory to PATH. in cmd.exe, -Spath worked ok, but -r just gave me back a command prompt (no repl).

where clojure.exe does give the appropriate path

hum that's a problem i encountered while fixing the problem you reported earlier, but i thought i fixed it, let me try again

hum works here, did you clone maybe a little while back ?

i've been a bad boy and pushed some partial changes at some point

i did a fresh clone right before trying just now

will try for a different clojure project folder

same result

mhh

check that the s in windows is there at https://github.com/cark/clojure-cli-portable/blob/6158e69cf30611b0744ac3c6e3399a4ddb779af8/src/clojure.nim#L138

what's your nim --version ? (though that should not matter at all but i can switch to it and try)

did you restart your console window after setting the path ?

i tried pointing the path to out/clojure-cli and it works too

nim compiler 0.20.2

ok let me switch to it (though i tried quite a few just now)

the s is in "windows" on line 138

i did try from a fresh prompt, but will try again

is it 32bit nim or 64 ?

x64 64 bit

ah wait

how do i check that?

ah that's a difference, i wonder why i'm on 32bits

it says amd64

from output of nim --version

works with amd64 compiler too

which clojure project did you try with?

your example, which is in issues/sogaiu1

and i switched to it for my own clojure programming too

i will try rebooting

damn that's not a good user experience =)

want to try my own binaries maybe ? i'll upload them

https://github.com/cark/clojure-cli-portable/releases/tag/v0.0.2

unfortunately, no change -- sure i'll try your binaries

also maybe you have some bad data in .cpcache but it's a long shot

same result -- i will look into .cpcache content

in one case, there was no .cpcache -- in another project there was, so i removed it and tried again -- unfortunately, same result

clojure -Sverbose -A:sock -r will give you a bit more info, but not much

so that means it doesn't even reach the step where it builds the cache

ah, one of the cases was my fault -- that wasn't a valid directory to test -- sorry for the other case, i see various paths followed by the message "Refreshing classpath", then the command prompt

oh so it works then =)

pfiuh you got me worried for a minute there =)

i was stumped on this one =)

thanks for persisting through it !

sorry to be unclear -- it still has problems

it's just that one of the project directories i was testing was invalid

it still has problems with the other one

oh

i also tried another project: https://github.com/seancorfield/depstar

i will try in a vm to compare

i still need to test the latest changes to depstar

might be able to use it again, and still produce cljdocs

if you wait a bit for more tests, i'll add a bunch of print statements to see how it fails

ah i found somethign that might be a problem in a machine dependent way, checking it out

@sogaiu pushed possible fix, with more verbosity and updated binaries too

i am not seeing any difference after pulling and rebuilding -- when you say updated binaries, are they on the releases page?

yes, but there should be some differences in the code

doing -Sverbose should turn on more verbosity?

wait i found one of my projects exhibiting the same issue

so i can take it from there

yes

ah ok

so it's not fixed, but i've got a test case now !

hurray for reproducibility 😉

for the record, depstar exhibited the same behavior on a physical machine windows 10 pro as well as a vm window 10 home

i was only typing clojure -r (or with -Sverbose)

oh i'll check on it too (depstar)

pushed a possible fix

i can start a repl on depstar

hurray! it works here too 🙂

weee !

thank you so much =)

thank you! it also works on my other test project 🙂

i'll go and make a test library with depstar, i promised i would test it

sounds like a good idea

LMK if you have questions / need help there...

actually i WAS using it, had to abandon it for cljdocs

I know. You said 🙂

next.jdbc started to rely on java.data and that's when I tripped over the same problem.

Which is now fixed 🙂

gonna make a library template and push it on clojars with docs on the one function it'll include

@carkh hoping I'll have a chance to look at your stuff at some point this week

@alexmiller nice thanks !