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
mysql2 fails to build, ST_CONTINUE error #3795
Comments
@saizai I don't know what the impact of I was able to install on Trusty as follows, so again, I wonder whether this is an RVM issue:
|
Same result. @mpapis?
|
Hi. Trying out rbx for the first time one of my home projects ( just to try out Rubinius) I'm running into the same issue building mysql2 gem on
Just for the heck of it, I tried gem install mysql ( NOT mysql2) and it worked just fine with Rubinius. Also the same gem (mysql2) is being built fine using MRI 1.9.3-p551, 2.1.5, 2.5.1 and 2.6.0-preview2 . So I'm fairly certain MySQL and rbenv setup are not the cause. However - I was able to install mysql2 -v 0.4.10 with rbx 3.107 Any ideas what else I could try to get mysql2 v 0.5.2 install? Thank you |
In general, the MRI C-API for Rubinius is deprecated, but that doesn't mean it will be going anywhere soon. Compatibility for C-extensions will continue to be evaluated on a case-by-case basis. However, C-extensions that depend on functions that examine or manipulate built-in MRI data structures will never be supported. The focus for Rubinius in the near term is on the following capabilities:
Contributions in the form of PRs for any of the areas of focus above are appreciated. |
The text was updated successfully, but these errors were encountered: