-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
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
in `find_type': unable to resolve type 'intptr_t' (TypeError) #166
Comments
ah,I think I found this reason.
And the all gemspec on there require
|
BTW, seeing_is_believing's version is |
Hi, I'm not sure how to get everything working on all the different systems that need to run it. I'm pretty sure I can get it if I drop Windows support and monkey patch the FFI gem to understand the ARM processors (I do that on my machine so that I can at least use it still). Unfortunately, child process management just doesn't behave consistently across the different operating systems, and the majority of effort involved in this project now is trying to debug that, which is super painful and hasn't yielded much success. I did rewrite it to just use Ruby's Anyway, I've put bursts of effort into figuring it out a bunch of different times, and kinda feel like I don't know what to do now 😞 🤔 maybe if I made it a little bit dumber (eg not recording which side closed a stream) I could get 🤔 oh, maybe also try pointing at the master branch on here instead of at Rubygems. There's some work on master, I think, which I didn't publish b/c it wasn't passing, but it's probably more likely to be correct. Like it should mostly work on Windows, even though the tests don't pass. You might get zombie processes, if you set a timeout and it kill the children, I can't remember if that's still a problem or not, I had it fixed at one point. |
Softare:Emacs 27.2
System: Win10
and the error log
Before I installed seeing_is_believing, I installed ffi-1.15.4.
But When typed gem install seeing_is_believing, ffi-1.11.3 was still be installed.
I think it is the gem's problem
The text was updated successfully, but these errors were encountered: