Latest puma gem cannot be installed on Fedora 22 without rvm #3477
Comments
imtayadeway
added a commit
to imtayadeway/manageiq
that referenced
this issue
Jul 16, 2015
Reverting back to the old web server so we can work on the following issues in a branch outside of master: ManageIQ#3477 ManageIQ#3468 ManageIQ#3444
|
@petrblaho do you know if this is still an issue with 2.12.1? |
|
@imtayadeway puma 2.12.1 and 2.12.2 compiles its extension fine. But looking at imtayadeway@2d8a094#diff-8b7db4d5cc4b8f6dc8feb7030baa2478R44 - thin in version 1.3.1 have the same issue as puma 2.12.0. Why it is needed to pin its version to 1.3.1 when there is thin 1.6.3 and it installs fine? Is that old need for rails 3 dependencies? But anyway newest puma works... |
|
@petrblaho good to hear! I'll mark this as solved then when the puma PR is merged. Can you open a new issue for thin if that is still a problem? |
|
@jrafanie since this issue was resolved without any code being changed, can this issue be closed? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Puma gem version 2.12.0 was released on July 14 and it has issues compiling C extension - see puma/puma#737 .
The reason looks like different (more strict) set of flags for gcc in Fedora.
rvm overrides these and installing puma 2.12.0 works with it.
Temporary solution would be pinning puma version at 2.11.3 (latest before 2.12.0) in Gemfile until puma is released with compilable C extension.
The text was updated successfully, but these errors were encountered: