You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, I suppose you can consider this a "port" of an issue from Yudai's original Gotty - see yudai/gotty#330. Basically, we can get it to compile, but a simple command like "gotty top" gives "Failed to execute command".
I realise that for most use cases, the solution will either be:
Use a more recent version
Use one of the prebuilt binaries of 1.0.1
and indeed the original issue was closed when OP went with option 1.
Neither of those are an option for me. My project hooks into the 1.0.1 code (and particularly Hterm) in a very specific way, and my new dev environment is Windows ARM64 WSL, for which there isn't a prebuilt binary for 1.0.1. Thus I needed a 1.0.1 ARM64 Linux binary.
I've forked and tweaked the 1.0.1 release - https://github.com/Loccy/gotty/tree/release-1.0 - so one can get a build out of it with relatively new tools. This is party based on what I've seen in other forks, applied to 1.0.1. And I was able to get it to spit out an ARM64 binary which seems to load, run, deliver a web page - but seems to fail to start any processes with that "Failed to execute command" message.
I freely admit I know how to spell "Go" and that's about it, so it is possible I was doing something dim and the reason my binary (and the one from the other issues board) didn't work was due to my own lack of understanding. But if someone could point me in the right direction I'd really appreciate it.
The text was updated successfully, but these errors were encountered:
So, I suppose you can consider this a "port" of an issue from Yudai's original Gotty - see yudai/gotty#330. Basically, we can get it to compile, but a simple command like "gotty top" gives "Failed to execute command".
I realise that for most use cases, the solution will either be:
and indeed the original issue was closed when OP went with option 1.
Neither of those are an option for me. My project hooks into the 1.0.1 code (and particularly Hterm) in a very specific way, and my new dev environment is Windows ARM64 WSL, for which there isn't a prebuilt binary for 1.0.1. Thus I needed a 1.0.1 ARM64 Linux binary.
I've forked and tweaked the 1.0.1 release - https://github.com/Loccy/gotty/tree/release-1.0 - so one can get a build out of it with relatively new tools. This is party based on what I've seen in other forks, applied to 1.0.1. And I was able to get it to spit out an ARM64 binary which seems to load, run, deliver a web page - but seems to fail to start any processes with that "Failed to execute command" message.
I freely admit I know how to spell "Go" and that's about it, so it is possible I was doing something dim and the reason my binary (and the one from the other issues board) didn't work was due to my own lack of understanding. But if someone could point me in the right direction I'd really appreciate it.
The text was updated successfully, but these errors were encountered: