Error forkexec homepi.cachejaguarsdkbintoit.compil...
# help
q
Does this seem like a path issue? just installed jag using GO, but i pulled the raspi sdk by cloning the jaguar repo and editing setup.go to fetch the raspi SDK and ran the setup that way. Error: fork/exec /home/pi/.cache/jaguar/sdk/bin/toit.compile: no such file or directory
When i run
jag run app.toit
, nothing happens in the monitor session.
I should also say that
jag flash
and
jag monitor
works fine
f
Interesting.
Normally, the
jag setup
should have set up the SDK.
Could you verify if
/home/pi/.cache/jaguar/sdk/bin/toit.compile
exists?
If it does, can you run it with
--help
?
If that fails with the same error message, then it's probably a version conflict.
That is, the OS version (specifically libc) you are using might not work with the
toit.compile
executable.
q
It does. Alright, let me fire up my laptop real quick (on the bus atm)
f
no worries.
I need to leave soon, so I might not be able to follow up for the next hours too.
q
Alright then, I'll leave a post either way. Thanks a lot for the quick response
f
If it's an OS mismatch, the easiest would be to upgrade the raspberry pi OS. (assuming it's an older one).
Yes. Please do so! Also keep pinging if it looks like I have forgotten.
At some point I will try to figure out why our
static
compilation isn't working...
q
But basically installing the sdk using jag setup is enough if jag is installed with go?
f
Yes. I think so.
The
no such file or directory
is almost certainly a libc (or something similar) it can't find.
q
Cool, cheers 😊
Seems like that is the case here 🙂
I will clean everything and start from scratch
f
Which version do you use?
Which raspberry pi? Which OS?
32/64 bits?
q
raspberry pi 4, Debian 64-bit
f
are you using the 64-bit version of Jaguar?
q
Installed it using go, so not 100% sure. Running
jag setup
outputs the following:
f
Could you do a
file /home/pi/.cache/jaguar/sdk/bin/toit.compile
?
I'm wondering if Jaguar actually supports downloading for the Raspberry Pi.
q
f
I think that's the Linux SDK.
The easiest is probably to just replace the SDK by hand.
q
On it! 🙂
f
Copy code
rm -rf /home/pi/.cache/jaguar/sdk
cd /tmp
wget https://github.com/toitlang/toit/releases/download/v2.0.0-alpha.44/toit-rpi64.tar.gz
tar x -f toit-rpi64.tar.gz
mv toit /home/pi/.cache/jaguar/sdk
should be something like this.
sorry. I didn't catch this earlier...
"fun" thing is, that I even wrote a PR 2 weeks ago that would have caught this: https://github.com/toitlang/jaguar/pull/305
q
Totally ok, I actually attempted this earlier, by modifying and hard-coding the following line https://github.com/toitlang/jaguar/blob/main/cmd/jag/commands/setup.go#L27
f
That should work too.
You would need to remove the old one, though.
jag setup
first checks whether there is already an SDK with the correct version.
(No check for the arch, though).
q
Done, seems like a 32-bit version is pulled anyway, or?
f
I think that's true.
However, the esptool in the
tools
folder is different.
That one should be 64bits.