You are not logged in.
I've finally decided to install Ruby 2.1 but it broke some Ruby/Tk apps I use.
I've checked the changelog for Ruby 2.1 and the Ruby documentation and it seems that Tk is still included in the stdlib.
It can't be a problem only I have since the package for Ruby 2.1 does not even list tk as a dependency anymore.
The real question is, why? Is it an Arch issue or maybe they haven't ported the Tk module to 2.1 yet? Tk is part of the Ruby standard library and as such should be automatically included with any Ruby installation (having Tk installed should be optional, though).
Please excuse me if I'm being ignorant but I don't hang around the Ruby community too much. Thanks.
Offline
Maybe it isn't included by default anymore? Try to add --with-ext=tk to the configure line in the PKGBUILD and rebuild it.
Or maybe it detects tcl/tk during the configure run, so it might be enough to build ruby while the packages are installed (e.g. added as makedepends)
https://projects.archlinux.org/svntogit … 110e6780d1
remove ruby/tk support because it is broken, add patch to fix installing gem from file without dependencies
You could downgrade tcl/tk, then rebuild ruby with tk I think.
Last edited by progandy (2014-02-01 09:40:43)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
I've finally decided to install Ruby 2.1 but it broke some Ruby/Tk apps I use......The real question is, why? Is it an Arch issue.....
As you've heard it isn't an Arch only issue. To me it points out that Ruby is a minor language and not in the same league as perl, tcl and python. Tcl/Tk 8.6 beta was in common use for several years and was finally declared the stable official release in Dec 2012. Yet in the spring of 2014 ruby still segfaults with "require tk". Almost a year ago the following appeared on the ruby dev list
[ruby-trunk - Bug #8000] "require 'tk'" segfaults on 64-bit linux with Tk 8.6
E4f967492dbd03c526cc9b397e68021d?d=identicon&s=25 nagai (Hidetoshi Nagai) (Guest) on 2013-03-08 06:12 (Received via mailing list)
Issue #8000 has been updated by nagai (Hidetoshi Nagai).
First of all, current Ruby/Tk cannot support Tcl/Tk8.6. Please see
[ruby-talk:395829].
But, I don't know whether this trouble belongs to the "tailcall" problem
or not.
Does the same trouble occur with Tcl/Tk8.5 ? If so, tcltklib may not
follow the changes on Ruby's core.
Of course, I must fix this bug and should support Tcl/Tk8.6.
However, I don't have enough time to work on it,
and unfortunately I have no idea to avoid the "tailcall" problem now.Apparently they still can't figure out the tail call problem.
Last edited by sitquietly (2014-02-01 18:37:38)
Offline