Ferret talk - Aug 2007 - ERROR: While executing gem ... (Gem::Installer::ExtensionBu

Hi all,

Sorry if this is answered somewhere -- I am new to ruby and to linux,
and can''t figure it out:

When I try to install ferret (see below), I get ERROR:  While executing
gem ... (Gem::Installer::ExtensionBuildError).  Same thing happens for
any version I pick from th list.

I am using:
gcc (GCC) 4.1.2 (Ubuntu 4.1.2-0ubuntu4)
ruby 1.8.5 (2006-08-25) [i486-linux]
gem 0.9.4

No idea how to fix this -- please help!

Thanks,

Geth

=======================================================

gethryn at gethryn-desktop:~/rails_space$ sudo gem install ferret
Password:
Select which gem to install for your platform (i486-linux)
 1. ferret 0.11.4 (ruby)
 2. ferret 0.11.4 (mswin32)
 3. ferret 0.11.3 (ruby)
 4. ferret 0.11.2 (ruby)
 5. Skip this gem
 6. Cancel installation
> 1
Building native extensions.  This could take a while...
ERROR:  While executing gem ... (Gem::Installer::ExtensionBuildError)
    ERROR: Failed to build gem native extension.

ruby extconf.rb install ferret
extconf.rb:11:in `require'': no such file to load -- mkmf (LoadError)
        from extconf.rb:11


Gem files will remain installed in
/usr/lib/ruby/gems/1.8/gems/ferret-0.11.4 for inspection.
Results logged to
/usr/lib/ruby/gems/1.8/gems/ferret-0.11.4/ext/gem_make.out
gethryn at gethryn-desktop:~/rails_space$
-- 
Posted via http://www.ruby-forum.com/.

> ruby extconf.rb install ferret
> extconf.rb:11:in `require'': no such file to load -- mkmf
(LoadError)
>         from extconf.rb:11
Geth,

i would assume, your ruby setup is broken. at least for root.
are you able to compile other extension or install other
gems? mkmf is a basic library of ruby, i''ve got it automatically
installed by ruby at

/usr/lib/ruby/1.8/mkmf.rb

are you able to open a irb session and require mkmf
manually? did you check, if that file exists in your ruby
1.8 folder? maybe you should reinstall ruby.

and did you check the log file?

/usr/lib/ruby/gems/1.8/gems/ferret-0.11.4/ext/gem_make.out

Ben

On Tue, Aug 28, 2007 at 09:45:28AM +0200, Benjamin Krause
wrote:
> > ruby extconf.rb install ferret
> > extconf.rb:11:in `require'': no such file to load -- mkmf
(LoadError)
> >         from extconf.rb:11
> 
> Geth,
> 
> i would assume, your ruby setup is broken. at least for root.
> are you able to compile other extension or install other
> gems? mkmf is a basic library of ruby, i''ve got it automatically
> installed by ruby at
> 
> /usr/lib/ruby/1.8/mkmf.rb
he''s on Ubuntu, which inherited the nice feature of having Ruby split
up
in several packages from Debian :(

mkmf is part of ruby1.8-dev.

Jens

-- 
Jens Kr?mer
webit! Gesellschaft f?r neue Medien mbH
Schnorrstra?e 76 | 01069 Dresden
Telefon +49 351 46766-0 | Telefax +49 351 46766-66
kraemer at webit.de | www.webit.de
 
Amtsgericht Dresden | HRB 15422
GF Sven Haubold, Hagen Malessa

Jens Kraemer wrote:
> he''s on Ubuntu, which inherited the nice feature of having Ruby
split up
> in several packages from Debian :(
> 
> mkmf is part of ruby1.8-dev.
> 
A THOUSAND THANK YOUS!  I can finish the book I am learning from now!

"Successfully installed ferret-0.11.4"

worked perfectly after I ran:

$ sudo apt-get install ruby1.8-dev

Thanks again,

Geth
-- 
Posted via http://www.ruby-forum.com/.

Debian makes the very civillised assumption that not everyone who runs
an application needs the ability to compile the application. Now if we
can just get a nice integration between apt and gem we would have a much
more usable and secure system.
On Tue, 2007-08-28 at 08:58 +0100, Jens Kraemer wrote:
> On Tue, Aug 28, 2007 at 09:45:28AM +0200, Benjamin Krause wrote:
> > > ruby extconf.rb install ferret
> > > extconf.rb:11:in `require'': no such file to load -- mkmf
> (LoadError)
> > >         from extconf.rb:11
> >
> > Geth,
> >
> > i would assume, your ruby setup is broken. at least for root.
> > are you able to compile other extension or install other
> > gems? mkmf is a basic library of ruby, i''ve got it
automatically
> > installed by ruby at
> >
> > /usr/lib/ruby/1.8/mkmf.rb
> 
> he''s on Ubuntu, which inherited the nice feature of having Ruby
split
> up
> in several packages from Debian :(
> 
> mkmf is part of ruby1.8-dev.
> 
> Jens
> 
> --
> Jens Kr?mer
> webit! Gesellschaft f?r neue Medien mbH
> Schnorrstra?e 76 | 01069 Dresden
> Telefon +49 351 46766-0 | Telefax +49 351 46766-66
> kraemer at webit.de | www.webit.de
> 
> Amtsgericht Dresden | HRB 15422
> GF Sven Haubold, Hagen Malessa
> _______________________________________________
> Ferret-talk mailing list
> Ferret-talk at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ferret-talk
> 
> 
Jobs Go Public is a limited company registered in England and Wales.
Registration Number 3716200. V.A.T Number 777 9458 52. Registered office; 12-16
Laystall Street, London, EC1R 4PF

Consider the environment; please don''t print this email unless you
really need to.

On 28.08.2007, at 12:38, Jeff Green wrote:
> Debian makes the very civillised assumption that not everyone who runs
> an application needs the ability to compile the application. Now if we
> can just get a nice integration between apt and gem we would have a  
> much
> more usable and secure system.
RubyGems and APT collide here. Debian''s policy is to favor APT over  
RubyGems, because they don''t like the idea of having two package  
management systems. Fair enough.

If you go the Debian way, you would install any gems via APT. Since  
not every gem (including Ferret) exists as a Debian package, your  
possibilities are quite limited with this approach.

The alternative is to install only ruby, ruby-dev and rubygems via  
APT and then install gems via RubyGems. However, for gems with native  
extenstions, you don''t have the luxury of dependecy-management.

For example: if you install the RMagick gem, you need to install the  
ImageMagick (dev) packages via APT first. Had you installed the  
RMagick gem via APT, this dependency would have been installed  
automatically.

On Debian you always need to install the development files for a  
package in order to compile anything against it. Development packages  
begin with "lib" and end with "-dev". So for MySQL and
ImageMagick
these are "libmysqlclient15-dev" and "libmagick9-dev",
respectively.

It''s important to note that, in order to compile _anything_ on  
Debian, the gcc, make, autoconf and build-essential packages must be  
installed first.

Cheers,
Andy