From: Dominik Maier Date: 2013-06-15T01:28:01+09:00 Subject: Re: Building Ruby --047d7b4144f81f81b004df1f4f3a Content-Type: text/plain; charset=ISO-8859-1 Wow. I didn't know that. Thanks. And yes you are right, 1.8 doen't require ruby. Thats how I build 2.0 the first time. 2013/6/14 AR (aka AleiPhoenix) > On Fri, Jun 14, 2013 at 04:06:23AM +0900, Stu wrote: > > What do you mean my minimal? I installed Ruby 2.1 on my Funtoo laptop the > > other day by hand. Simply set up my own environment. Also do this with > some > > scheme interpreters and so forth. Many people use RVM mainly to sync > legacy > > applications with a specific ruby patch level and gem version to avoid > > breakage. Also RVM deals with some edge cases where hand compiling may > be a > > bit more involved; for example rvm works great with FreeBSD and OSX where > > different compilers and POSIX utilities are as minimal as they come. > > > > ~Stu > > > > I doubt whether a *executable host ruby* is required for build ruby, So I > wondered. > > I've tried to compile 1.9.2-p320 and 2.0.0-p195 without any problems (both > are simplly configure and make), but... > > When I ran make distclean then configure and make, it complained about > 'executable host ruby is required. use --with-baseruby option'. > > I was starting realize that there must be something different before and > after running `make distclean`, so I diffed them. > > diff -dru ruby-2.0.0-p195/ ruby-2.0.0-p195.distcleaned/ > > Only in ruby-2.0.0-p195: encdb.h > Only in ruby-2.0.0-p195/ext/ripper: y.output > Only in ruby-2.0.0-p195: golf_prelude.c > Only in ruby-2.0.0-p195: insns.inc > Only in ruby-2.0.0-p195: insns_info.inc > Only in ruby-2.0.0-p195: known_errors.inc > Only in ruby-2.0.0-p195: node_name.inc > Only in ruby-2.0.0-p195: optinsn.inc > Only in ruby-2.0.0-p195: opt_sc.inc > Only in ruby-2.0.0-p195: optunifs.inc > Only in ruby-2.0.0-p195: .revision.time > Only in ruby-2.0.0-p195: transdb.h > Only in ruby-2.0.0-p195: vm.inc > Only in ruby-2.0.0-p195: vmtc.inc > > > Looks like some files have to be generated using a *existing ruby*. and > the source tarball already included them (for instance, known_errors.inc, > it's from template/known_errors.inc.tmpl, written in erb). When running > make distclean, those files are just be cleaned out. this should be the > reason. > > Anyway, according to some google answers, building 1.8.x which doesn't > require a existing ruby, then using --baseruby should do the trick. > > Correct me if I'm wrong. > > Thanks. > > -- > > AR (aka AleiPhoenix) > Twitter: @AccelReality > Wikipedia: AleiPhoenix > weblog: weblog.areverie.org > --047d7b4144f81f81b004df1f4f3a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Wow. I didn't know that. Thanks.
And yes= you are right, 1.8 doen't require ruby. Thats how I build 2.0 the firs= t time.


2013/6/14 AR (aka AleiPhoenix) <aleiphoenix@gmail.com>
On Fri, Jun 14, 2013 at 04:06:23AM +0900, Stu wrote:
> What do you mean my minimal? I installed Ruby 2.1 on my Funtoo laptop = the
> other day by hand. Simply set up my own environment. Also do this with= some
> scheme interpreters and so forth. Many people use RVM mainly to sync l= egacy
> applications with a specific ruby patch level and gem version to avoid=
> breakage. Also RVM deals with some edge cases where hand compiling may= be a
> bit more involved; for example rvm works great with FreeBSD and OSX wh= ere
> different compilers and POSIX utilities are as minimal as they come. >
> ~Stu
>

I doubt whether a *executable host ruby* is required for build ruby, = So I wondered.

I've tried to compile 1.9.2-p320 and 2.0.0-p195 without any problems (b= oth are simplly configure and make), but...

When I ran make distclean then configure and make, it complained about '= ;executable host ruby is required. use --with-baseruby option'.

I was starting realize that there must be something different before and af= ter running `make distclean`, so I diffed them.

diff -dru ruby-2.0.0-p195/ ruby-2.0.0-p195.distcleaned/

Only in ruby-2.0.0-p195: encdb.h
Only in ruby-2.0.0-p195/ext/ripper: y.output
Only in ruby-2.0.0-p195: golf_prelude.c
Only in ruby-2.0.0-p195: insns.inc
Only in ruby-2.0.0-p195: insns_info.inc
Only in ruby-2.0.0-p195: known_errors.inc
Only in ruby-2.0.0-p195: node_name.inc
Only in ruby-2.0.0-p195: optinsn.inc
Only in ruby-2.0.0-p195: opt_sc.inc
Only in ruby-2.0.0-p195: optunifs.inc
Only in ruby-2.0.0-p195: .revision.time
Only in ruby-2.0.0-p195: transdb.h
Only in ruby-2.0.0-p195: vm.inc
Only in ruby-2.0.0-p195: vmtc.inc


Looks like some files have to be generated using a *existing ruby*. and the= source tarball already included them (for instance, known_errors.inc, it&#= 39;s from template/known_errors.inc.tmpl, written in erb). When running mak= e distclean, those files are just be cleaned out. this should be the reason= .

Anyway, according to some google answers, building 1.8.x which doesn't = require a existing ruby, then using --baseruby should do the trick.

Correct me if I'm wrong.

Thanks.

--

AR (aka AleiPhoenix)
Twitter: @AccelReality
Wikipedia: AleiPhoenix
weblog: weblog.are= verie.org

--047d7b4144f81f81b004df1f4f3a--