We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First of all I must say I was amazed by this sumulation tool when I saw it on https://www.youtube.com/watch?v=mlrf1058ENY&list=PLuhRWgmPaHtRPl3Itt_YdHYA0g0Eup8hQ&index=4. Which is why I wanted to try it myself.
I'm using Gerbil v0.17 on Gambit v4.9.3 and when I launch gxpkg install github.com/vyzo/gerbil-simsub I get the following error:
Gerbil v0.17 on Gambit v4.9.3
gxpkg install github.com/vyzo/gerbil-simsub
➜ gxpkg install github.com/vyzo/gerbil-simsub ... install github.com/vyzo/gerbil-simsub ... build github.com/vyzo/gerbil-simsub *** ERROR IN gx#core-expand-ref% -- Syntax Error *** ERROR IN "simsub/flood.ss"@44.7 --- Syntax Error: Reference to unbound identifier ... form: (%#ref log-error) ... detail: log-error at "simsub/flood.ss"@44.7 Process exited with non-zero status 17920 (path:
Is there any "easy" way to get around that ?
The text was updated successfully, but these errors were encountered:
yeah, its bitrot, log-error is replaced by errorf. I will be updating it soon, as i plan to simulate the episub extensions, possibly this weekend.
Sorry, something went wrong.
glad to hear that, I'm looking forward :)
I started working on refactoring amd support for gs1.1/1.2 in #5
No branches or pull requests
First of all I must say I was amazed by this sumulation tool when I saw it on https://www.youtube.com/watch?v=mlrf1058ENY&list=PLuhRWgmPaHtRPl3Itt_YdHYA0g0Eup8hQ&index=4. Which is why I wanted to try it myself.
I'm using
Gerbil v0.17 on Gambit v4.9.3
and when I launchgxpkg install github.com/vyzo/gerbil-simsub
I get the following error:Is there any "easy" way to get around that ?
The text was updated successfully, but these errors were encountered: