Bugzilla Bug 234161

>>> Compiling source in /var/tmp/portage/media-sound/rubyripper-0.5.2/work/rubyripper-0.5.2 ...
Checking the NEEDED dependencies....
cdparanoia found...

Checking the OPTIONAL dependencies...
Testing support for the graphical frontend...
No protocol specified
/usr/lib64/ruby/site_ruby/1.8/gtk2.rb:13:in `init': Cannot open display: :0.0
(RuntimeError)
        from /usr/lib64/ruby/site_ruby/1.8/gtk2.rb:13
        from /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in
`gem_original_require'
        from /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in
`require'
        from ./configure:81:in `check_deps'
        from ./configure:164
 * ERROR: media-sound/rubyripper-0.5.2 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2360:  Called die
 * The specific snippet of code:
 *       ./configure ${myconf} || die "./configure failed";
 *  The die message:
 *   ./configure failed
 * If you need support, post the topmost build error, and the call stack if
relevant.
 * A complete build log is located at
'/var/log/portage/media-sound:rubyripper-0.5.2:20080807-091714.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/media-sound/rubyripper-0.5.2/temp/environment'.

Thanks,
Diego

Created an attachment (id=164623) [details]
rubyripper-0.5.3 ebuild modified from rubyripper-0.5.2.ebuild

I will attach the patch as the next attachment

Created an attachment (id=164624) [details]
patch necessary to get rubyripper-0.5.3 to emerge.

I created a local portage overlay and modified the ebuild and patch to allow
rubyripper-0.5.3 ebuild to be emerged.

Please test, and if I botched it, please explain to me why it is in error so I
can learn to help build ebuilds for the community.

The problem lies in how the check for gtk2 is done. Currently the
configure-script use a "require 'gtk2'". gtk2.rb makes a call to the function
GTK.init when loaded which fails if it cannot connect to a running X or if
DISPLAY is unset.

One solution here is to just remove the check since that line in configure have
no impact on if the gtk-gui is getting installed or not.

Created an attachment (id=164725) [details]
Patch to get configure working in non-X emerge

Proposed patch to get rubyripper to install in non-X emerge.Checks for gtk2 is
removed.

fixed in 0.5.3 by using Xeconf

I've just hit this now, with rubyripper-0.5.3

I'm building within a chroot (/chroot), using "mount --bind /tmp/ /chroot/tmp/"
allowed it to compile.

The error message was identical to that in the original bug report, except "No
protocol specified" was omitted.