From: Nigel Gilbert <n.gilbert@...>
Date: 2002-01-04T01:24:31+09:00
Subject: [ruby-talk:30137] Re: Problem compiling Ruby on Solaris

Wonderful.  It works!

[The solution was to remove the # on "#option nodynamic" in ext/Setup, 
so as not to compile dynamic extensions]


Having in mind the advice in the README:
> If you fail to compile ruby, please send the detailed error report with
> the error log and machine/OS type, to help others.
does this mean that the configure script should be changed for Solaris 
OSs, or is my system peculiar in some way?

Thanks for your help in getting over this problem.

Nigel


On Thursday, January 3, 2002, at 03:39 PM, ts wrote:

>>>>>> "N" == Nigel Gilbert <n.gilbert@soc.surrey.ac.uk> writes:
>
> N> OK, but can you give me a clue how to do this, or point me to some 
> docs
> N> which describe what I need to do?
>
>  You have in the README
>
>
>    * How to compile and install
>
>    This is what you need to do to compile and install Ruby:
>
>      1. If ./configure does not exist or is older than configure.in,
>         run autoconf to (re)generate configure.
>
>      2. Run ./configure, which will generate config.h and Makefile.
>
>      3. Edit defines.h if you need.  Probably this step will not need.
>
>      4. Remove comment mark(#) before the module names from ext/Setup 
> (or
>         add module names if not present), if you want to link modules
>         statically.
>
>         If you don't want to compile non static extension modules
>         (probably on architectures which does not allow dynamic 
> loading),
>         remove comment mark from the line "#option nodynamic" in
>         ext/Setup.
>
>      5. Run make.
>
>
>
> Guy Decoux
>
>
>
>
>
__________________________________________________________________________
Professor Nigel Gilbert, FREng, AcSS, Pro Vice-Chancellor and Professor 
of
Sociology, University of Surrey, Guildford GU2 7XH, UK. +44 (0)1483 
689173