Installing Redmine

[Craig White]

On Wed, 2010-02-24 at 22:09 -0700, Eric Cope wrote:
> so far...
> Redmine required:
> rack 1.0.1 (latest 1.1.0, had to use gem install rack -v 1.0.1)
> test_spec
> camping
> fcgi
> 
> I can not seem to install fcgi. here is the output...
> 
> ERROR:  Error installing fcgi:
>     ERROR: Failed to build gem native extension.
> 
> /usr/bin/ruby extconf.rb install fcgi
> checking for fcgiapp.h... no
> checking for fastcgi/fcgiapp.h... no
> *** extconf.rb failed ***
> Could not create Makefile due to some reason, probably lack of
> necessary libraries and/or headers.  Check the mkmf.log file for more
> details.  You may need configuration options.
> 
> Provided configuration options:
>     --with-opt-dir
>     --without-opt-dir
>     --with-opt-include
>     --without-opt-include=${opt-dir}/include
>     --with-opt-lib
>     --without-opt-lib=${opt-dir}/lib
>     --with-make-prog
>     --without-make-prog
>     --srcdir=.
>     --curdir
>     --ruby=/usr/bin/ruby
>     --with-fcgi-dir
>     --without-fcgi-dir
>     --with-fcgi-include
>     --without-fcgi-include=${fcgi-dir}/include
>     --with-fcgi-lib
>     --without-fcgi-lib=${fcgi-dir}/lib
> 
> 
> Gem files will remain installed
> in /usr/lib/ruby/gems/1.8/gems/fcgi-0.8.8 for inspection.
> Results logged
> to /usr/lib/ruby/gems/1.8/gems/fcgi-0.8.8/ext/fcgi/gem_make.out
----
and one more commentary...

If the intent was to package redmine as sort of a turnkey installation,
rails packaging is actually much better than what your experiences show
because it would have been relatively simple to configure
config/environment.rb to download and install the requisite gems on
first run (given the vast improvements of Rails 2.3.x, etc.)

I suspect that this project is somewhat out of date (just the
requirement of fcgi is a big hint).

I have to believe that somewhere in the config/environment.rb file are
the gem 'requires' which I suggested needed cleaning up and probably
something like...

  config.gem 'rack' 
    OR
  config.gem 'rack', :version => '~> 1.0.1'

would have solved the issue with requiring rack 1.0.1

Craig


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.