[ruby-core:76931] [Ruby trunk Bug#12681] Gemfied tk issue

[ruby-core:76931] [Ruby trunk Bug#12681] Gemfied tk issue

[v.ondruch]

Issue #12681 has been reported by Vit Ondruch.

----------------------------------------
Bug #12681: Gemfied tk issue
https://bugs.ruby-lang.org/issues/12681

* Author: Vit Ondruch
* Status: Open
* Priority: Normal
* Assignee: Yui NARUSE
* ruby -v: ruby 2.4.0dev (2016-08-16 trunk 55915) [x86_64-linux]
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
First of all, thank you for moving Tk into independent gem.

Nevertheless, I have one concern. So far, you left the tcltklib.so and tkutil.so under ruby lib directory. This is unfortunately major flaw, since the Tk gem is not one of the default gems. Hence, if you install more versions of Tk library, there might be collision among them.

Also, the "gem install tk" does not build the extension, so that is another source of possible issues.





-- 
https://bugs.ruby-lang.org/

[ruby-core:76934] [Ruby trunk Bug#12681] Gemfied tk issue

[hsbt]

Issue #12681 has been updated by Hiroshi SHIBATA.


>Also, the "gem install tk" does not build the extension, so that is another source of possible issues.

I missed configuration of tk.gemspec. It's fixed at tk-0.1.1 probably. Can you confirm it?

----------------------------------------
Bug #12681: Gemfied tk issue
https://bugs.ruby-lang.org/issues/12681#change-60163

* Author: Vit Ondruch
* Status: Open
* Priority: Normal
* Assignee: Yui NARUSE
* ruby -v: ruby 2.4.0dev (2016-08-16 trunk 55915) [x86_64-linux]
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
First of all, thank you for moving Tk into independent gem.

Nevertheless, I have one concern. So far, you left the tcltklib.so and tkutil.so under ruby lib directory. This is unfortunately major flaw, since the Tk gem is not one of the default gems. Hence, if you install more versions of Tk library, there might be collision among them.

Also, the "gem install tk" does not build the extension, so that is another source of possible issues.





-- 
https://bugs.ruby-lang.org/

[ruby-core:77056] [Ruby trunk Bug#12681] Gemfied tk issue

[v.ondruch]

Issue #12681 has been updated by Vit Ondruch.


Hiroshi SHIBATA wrote:
> >Also, the "gem install tk" does not build the extension, so that is another source of possible issues.
> 
> I missed configuration of tk.gemspec. It's fixed at tk-0.1.1 probably. Can you confirm it?

Yes, the 0.1.1 looks good. Thx.

----------------------------------------
Bug #12681: Gemfied tk issue
https://bugs.ruby-lang.org/issues/12681#change-60280

* Author: Vit Ondruch
* Status: Closed
* Priority: Normal
* Assignee: Yui NARUSE
* ruby -v: ruby 2.4.0dev (2016-08-16 trunk 55915) [x86_64-linux]
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
First of all, thank you for moving Tk into independent gem.

Nevertheless, I have one concern. So far, you left the tcltklib.so and tkutil.so under ruby lib directory. This is unfortunately major flaw, since the Tk gem is not one of the default gems. Hence, if you install more versions of Tk library, there might be collision among them.

Also, the "gem install tk" does not build the extension, so that is another source of possible issues.





-- 
https://bugs.ruby-lang.org/

[ruby-core:77057] [Ruby trunk Bug#12681][Open] Gemfied tk issue

[v.ondruch]

Issue #12681 has been updated by Vit Ondruch.

Status changed from Closed to Open

The r55950 does not resolve the issue completely. The make install does not work (neither the gem itself probably):

```
# make install DESTDIR=/builddir/build/BUILDROOT/ruby-2.4.0-0.1.r56008.fc26.x86_64

... snip ...

./miniruby -I./lib -I. -I.ext/common  ./tool/runruby.rb --extout=.ext  -- --disable-gems -r./x86_64-linux-fake ./tool/rbinstall.rb --make="make" --dest-dir="/builddir/build/BUILDROOT/ruby-2.4.0-0.1.r56008.fc26.x86_64" --extout=".ext" --mflags="" --make-flags="" --data-mode=0644 --prog-mode=0755 --installed-list .installed.list --mantype="doc" --install=all --rdoc-output=".ext/rdoc"
installing binary commands:   /usr/bin
installing base libraries:    /usr/lib64
installing arch files:        /usr/lib64/ruby/2.4.0/x86_64-linux
installing pkgconfig data:    /usr/lib64/pkgconfig
installing command scripts:   /usr/bin
installing library scripts:   /usr/lib64/ruby/2.4.0
installing common headers:    /usr/include/ruby-2.4.0
installing manpages:          /usr/share/man/man1
installing extension objects: /usr/lib64/ruby/2.4.0/x86_64-linux
installing extension objects: /usr/lib64/ruby/site_ruby/2.4.0/x86_64-linux
installing extension objects: /usr/lib64/ruby/vendor_ruby/2.4.0/x86_64-linux
installing extension headers: /usr/include/ruby-2.4.0/x86_64-linux
installing extension scripts: /usr/lib64/ruby/2.4.0
installing extension scripts: /usr/lib64/ruby/site_ruby/2.4.0
installing extension scripts: /usr/lib64/ruby/vendor_ruby/2.4.0
installing extension headers: /usr/include/ruby-2.4.0/ruby
installing default gems:      /usr/lib64/ruby/gems/2.4.0 (build_info, cache, doc, extensions, gems, specifications)
                              bigdecimal 1.2.8
                              io-console 0.4.6
                              json 2.0.2
                              psych 2.1.0
                              rdoc 4.2.1
installing bundle gems:       /usr/lib64/ruby/gems/2.4.0 (build_info, cache, doc, extensions, gems, specifications)
                              did_you_mean 1.0.2
                              minitest 5.9.0
                              rake 11.2.2
                              power_assert 0.3.0
                              test-unit 3.2.1
                              tk 0.1.1
./tool/rbinstall.rb:273:in `initialize': No such file or directory @ rb_sysopen - /builddir/build/BUILDROOT/ruby-2.4.0-0.1.r56008.fc26.x86_64/usr/lib64/ruby/gems/2.4.0/extensions/x86_64-linux/2.4.0-static/tk-0.1.1/gem.build_complete (Errno::ENOENT)
	from ./tool/rbinstall.rb:273:in `open'
	from ./tool/rbinstall.rb:273:in `open_for_install'
	from ./tool/rbinstall.rb:769:in `block (2 levels) in <main>'
	from /builddir/build/BUILD/ruby-2.4.0-r56008/lib/rubygems/specification.rb:821:in `block in each_spec'
	from /builddir/build/BUILD/ruby-2.4.0-r56008/lib/rubygems/specification.rb:743:in `block (2 levels) in each_gemspec'
	from /builddir/build/BUILD/ruby-2.4.0-r56008/lib/rubygems/specification.rb:742:in `each'
	from /builddir/build/BUILD/ruby-2.4.0-r56008/lib/rubygems/specification.rb:742:in `block in each_gemspec'
	from /builddir/build/BUILD/ruby-2.4.0-r56008/lib/rubygems/specification.rb:741:in `each'
	from /builddir/build/BUILD/ruby-2.4.0-r56008/lib/rubygems/specification.rb:741:in `each_gemspec'
	from /builddir/build/BUILD/ruby-2.4.0-r56008/lib/rubygems/specification.rb:819:in `each_spec'
	from ./tool/rbinstall.rb:758:in `block in <main>'
	from ./tool/rbinstall.rb:823:in `block in <main>'
	from ./tool/rbinstall.rb:820:in `each'
	from ./tool/rbinstall.rb:820:in `<main>'
uncommon.mk:277: recipe for target 'do-install-all' failed
make: *** [do-install-all] Error 1
```

----------------------------------------
Bug #12681: Gemfied tk issue
https://bugs.ruby-lang.org/issues/12681#change-60281

* Author: Vit Ondruch
* Status: Open
* Priority: Normal
* Assignee: Yui NARUSE
* ruby -v: ruby 2.4.0dev (2016-08-16 trunk 55915) [x86_64-linux]
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
First of all, thank you for moving Tk into independent gem.

Nevertheless, I have one concern. So far, you left the tcltklib.so and tkutil.so under ruby lib directory. This is unfortunately major flaw, since the Tk gem is not one of the default gems. Hence, if you install more versions of Tk library, there might be collision among them.

Also, the "gem install tk" does not build the extension, so that is another source of possible issues.





-- 
https://bugs.ruby-lang.org/

[ruby-core:77058] [Ruby trunk Bug#12681] Gemfied tk issue

[v.ondruch]

Issue #12681 has been updated by Vit Ondruch.


Moreover, I still see the tcltklib.so and tkutil.so installed into /usr/lib64/ruby/2.4.0/x86_64-linux/ but they should not be there at all.


----------------------------------------
Bug #12681: Gemfied tk issue
https://bugs.ruby-lang.org/issues/12681#change-60282

* Author: Vit Ondruch
* Status: Open
* Priority: Normal
* Assignee: Yui NARUSE
* ruby -v: ruby 2.4.0dev (2016-08-16 trunk 55915) [x86_64-linux]
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
First of all, thank you for moving Tk into independent gem.

Nevertheless, I have one concern. So far, you left the tcltklib.so and tkutil.so under ruby lib directory. This is unfortunately major flaw, since the Tk gem is not one of the default gems. Hence, if you install more versions of Tk library, there might be collision among them.

Also, the "gem install tk" does not build the extension, so that is another source of possible issues.





-- 
https://bugs.ruby-lang.org/

[ruby-core:77059] [Ruby trunk Bug#12681] Gemfied tk issue

[v.ondruch]

Issue #12681 has been updated by Vit Ondruch.


Actually this line is suspicious:

https://github.com/ruby/ruby/blob/trunk/ext/extmk.rb#L568

It expands to ```$(topdir)/.ext/gems``` and creates the ```$(topdir)``` directory indeed. But that doesn't look to be the original intention here. Tried to revert to ```.ext/gems``` but it doesn't really make a difference ...


----------------------------------------
Bug #12681: Gemfied tk issue
https://bugs.ruby-lang.org/issues/12681#change-60283

* Author: Vit Ondruch
* Status: Open
* Priority: Normal
* Assignee: Yui NARUSE
* ruby -v: ruby 2.4.0dev (2016-08-16 trunk 55915) [x86_64-linux]
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
First of all, thank you for moving Tk into independent gem.

Nevertheless, I have one concern. So far, you left the tcltklib.so and tkutil.so under ruby lib directory. This is unfortunately major flaw, since the Tk gem is not one of the default gems. Hence, if you install more versions of Tk library, there might be collision among them.

Also, the "gem install tk" does not build the extension, so that is another source of possible issues.





-- 
https://bugs.ruby-lang.org/

[ruby-core:77100] [Ruby trunk Bug#12681] Gemfied tk issue

[v.ondruch]

Issue #12681 has been updated by Vit Ondruch.

Assignee changed from Yui NARUSE to Nobuyoshi Nakada

It seems that r55966 is part of the problem. The place [1] where the block could be executed was removed in favor of [2]. Unfortunately, that path is never reached, since the tk gem contains extconf.rb and hence the condition [3] is true.

Reverting r55966 helped me to place the compiled extension into proper places.

Also, I think that the removal of ```FileUtils::makedirs("#$extout/gems")``` [4] should be enough to avoid the creation of the ```$(topdir)``` directory. The appropriate directories are created later by ```extmake``` anyway


[1] https://github.com/ruby/ruby/commit/438f52d1a4aa03650a53911a66f7d81c4fc20d38#diff-14d8ef4026c4b825d1e5a95429bf4156L244
[2] https://github.com/ruby/ruby/commit/438f52d1a4aa03650a53911a66f7d81c4fc20d38#diff-14d8ef4026c4b825d1e5a95429bf4156L228
[3] https://github.com/ruby/ruby/commit/438f52d1a4aa03650a53911a66f7d81c4fc20d38#diff-14d8ef4026c4b825d1e5a95429bf4156L220
[4] https://github.com/ruby/ruby/blob/trunk/ext/extmk.rb#L568

----------------------------------------
Bug #12681: Gemfied tk issue
https://bugs.ruby-lang.org/issues/12681#change-60321

* Author: Vit Ondruch
* Status: Open
* Priority: Normal
* Assignee: Nobuyoshi Nakada
* ruby -v: ruby 2.4.0dev (2016-08-16 trunk 55915) [x86_64-linux]
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
First of all, thank you for moving Tk into independent gem.

Nevertheless, I have one concern. So far, you left the tcltklib.so and tkutil.so under ruby lib directory. This is unfortunately major flaw, since the Tk gem is not one of the default gems. Hence, if you install more versions of Tk library, there might be collision among them.

Also, the "gem install tk" does not build the extension, so that is another source of possible issues.





-- 
https://bugs.ruby-lang.org/

[ruby-core:77101] [Ruby trunk Bug#12681] Gemfied tk issue

[nobu]

Issue #12681 has been updated by Nobuyoshi Nakada.


Do you install after `make extract-gems` or without it?

----------------------------------------
Bug #12681: Gemfied tk issue
https://bugs.ruby-lang.org/issues/12681#change-60322

* Author: Vit Ondruch
* Status: Open
* Priority: Normal
* Assignee: Nobuyoshi Nakada
* ruby -v: ruby 2.4.0dev (2016-08-16 trunk 55915) [x86_64-linux]
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
First of all, thank you for moving Tk into independent gem.

Nevertheless, I have one concern. So far, you left the tcltklib.so and tkutil.so under ruby lib directory. This is unfortunately major flaw, since the Tk gem is not one of the default gems. Hence, if you install more versions of Tk library, there might be collision among them.

Also, the "gem install tk" does not build the extension, so that is another source of possible issues.





-- 
https://bugs.ruby-lang.org/

[ruby-core:77111] [Ruby trunk Bug#12681][Assigned] Gemfied tk issue

[v.ondruch]

Issue #12681 has been updated by Vit Ondruch.

Status changed from Closed to Assigned

Vit Ondruch wrote:
> Also, I think that the removal of `FileUtils::makedirs("#$extout/gems")` [4] should be enough to avoid the creation of the `$(topdir)` directory. The appropriate directories are created later by `extmake` anyway

This was reported separately as #12714 and fixed by r56042



Nobuyoshi Nakada wrote:
> Do you install after `make extract-gems` or without it?

Never heard about "extract-gems" nor I understand why I should use it, when I build from the snapshot tarball. So far ```make & make install``` was always enough.

Anyway, your recent changes probably fix the issue but broke some RubyGems tests:

http://www.rubyist.net/~akr/chkbuild/debian/ruby-trunk/log/20160831T110500Z.fail.html.gz

----------------------------------------
Bug #12681: Gemfied tk issue
https://bugs.ruby-lang.org/issues/12681#change-60334

* Author: Vit Ondruch
* Status: Assigned
* Priority: Normal
* Assignee: Nobuyoshi Nakada
* ruby -v: ruby 2.4.0dev (2016-08-16 trunk 55915) [x86_64-linux]
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
First of all, thank you for moving Tk into independent gem.

Nevertheless, I have one concern. So far, you left the tcltklib.so and tkutil.so under ruby lib directory. This is unfortunately major flaw, since the Tk gem is not one of the default gems. Hence, if you install more versions of Tk library, there might be collision among them.

Also, the "gem install tk" does not build the extension, so that is another source of possible issues.





-- 
https://bugs.ruby-lang.org/

[ruby-core:77113] [Ruby trunk Bug#12681][Closed] Gemfied tk issue

[v.ondruch]

Issue #12681 has been updated by Vit Ondruch.

Status changed from Assigned to Closed

It seems that r56049 and r56050 fixes the remaining issues for me. Thx.

----------------------------------------
Bug #12681: Gemfied tk issue
https://bugs.ruby-lang.org/issues/12681#change-60336

* Author: Vit Ondruch
* Status: Closed
* Priority: Normal
* Assignee: Nobuyoshi Nakada
* ruby -v: ruby 2.4.0dev (2016-08-16 trunk 55915) [x86_64-linux]
* Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN
----------------------------------------
First of all, thank you for moving Tk into independent gem.

Nevertheless, I have one concern. So far, you left the tcltklib.so and tkutil.so under ruby lib directory. This is unfortunately major flaw, since the Tk gem is not one of the default gems. Hence, if you install more versions of Tk library, there might be collision among them.

Also, the "gem install tk" does not build the extension, so that is another source of possible issues.





-- 
https://bugs.ruby-lang.org/