Hi all,
It seems that since Ruby 2.1, Ruby can use GMP [1] to make some math operation faster. Should we enable it? Any experience?
Vít
So, I enabled this in Ruby and as it turns out, it has unexpected side effects in broken builds of binary rubygem- packages. This is the mkmf.log of one of affected packages:
~~~
"pkg-config --exists libffi" | pkg-config --libs libffi => "-lffi \n" "gcc -o conftest -I/usr/include -I/usr/include/ruby/backward -I/usr/include -I. -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -mcet -fcf-protection conftest.c -L. -L/usr/lib64 -L. -Wl,-z,relro -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -fstack-protector -rdynamic -Wl,-export-dynamic -m64 -lruby -lpthread -lgmp -ldl -lcrypt -lm -lc" /usr/bin/ld: cannot find -lgmp collect2: error: ld returned 1 exit status checked program was: /* begin */ 1: #include "ruby.h" 2: 3: int main(int argc, char **argv) 4: { 5: return 0; 6: } /* end */
~~~
Apparently, the "-lgmp" option is the culprit, since there is not the gmp-devel package installed everywhere. Until this is resolved upstream [1], it seems I have to revert the GMP unless I want to patch rbconfig.rb values.
Vít
[1] https://bugs.ruby-lang.org/issues/14422#note-6
Dne 19.1.2018 v 10:49 Vít Ondruch napsal(a):
Hi all,
It seems that since Ruby 2.1, Ruby can use GMP [1] to make some math operation faster. Should we enable it? Any experience?
Vít
ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org To unsubscribe send an email to ruby-sig-leave@lists.fedoraproject.org
This was resolved upstream, so GMP will be re-enabled in Rawhide as soon as there is new build. Don't plan it ATM, because this is not super important.
V.
Dne 1.3.2018 v 12:13 Vít Ondruch napsal(a):
So, I enabled this in Ruby and as it turns out, it has unexpected side effects in broken builds of binary rubygem- packages. This is the mkmf.log of one of affected packages:
"pkg-config --exists libffi" | pkg-config --libs libffi => "-lffi \n" "gcc -o conftest -I/usr/include -I/usr/include/ruby/backward -I/usr/include -I. -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -mcet -fcf-protection conftest.c -L. -L/usr/lib64 -L. -Wl,-z,relro -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -fstack-protector -rdynamic -Wl,-export-dynamic -m64 -lruby -lpthread -lgmp -ldl -lcrypt -lm -lc" /usr/bin/ld: cannot find -lgmp collect2: error: ld returned 1 exit status checked program was: /* begin */ 1: #include "ruby.h" 2: 3: int main(int argc, char **argv) 4: { 5: return 0; 6: } /* end */
Apparently, the "-lgmp" option is the culprit, since there is not the gmp-devel package installed everywhere. Until this is resolved upstream [1], it seems I have to revert the GMP unless I want to patch rbconfig.rb values.
Vít
[1] https://bugs.ruby-lang.org/issues/14422#note-6
Dne 19.1.2018 v 10:49 Vít Ondruch napsal(a):
Hi all,
It seems that since Ruby 2.1, Ruby can use GMP [1] to make some math operation faster. Should we enable it? Any experience?
Vít
ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org To unsubscribe send an email to ruby-sig-leave@lists.fedoraproject.org
ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org To unsubscribe send an email to ruby-sig-leave@lists.fedoraproject.org
ruby-sig@lists.fedoraproject.org