From: Kero <kero@...>
Date: 2005-10-01T19:01:48+09:00
Subject: Re: cross-compiling ruby

> So, finally the question. Before I go off and spend a lot of time at it,
> has anyone explored what it will take to cross-compile ruby? For what
> it's worth the host is x86 and the target is ppc.

Ruby needs a lot of headerfiles to compile all libraries. Your best bet
for those is to set up a "cross-root" with all libs and includes that
you need.

/cross/
/cross/usr/include/
/cross/usr/lib/
....

If you have a packaging system for the target platform, it may be as
easy as `pkg -dest /cross` (assuming pkg runs on your compiling
machine; in my case (ipkg for familiar-linux on arm4) it did).

This will never solve the issue with setpgrep and friends, since the
resulting testprogram can't be executed locally. It's a shame ./configure
has no option to override those cross-compiling things. See the other
followup for a solution to some of those.

--

I had the luck to have a networked machine available with a huge NFS
mount on it with the dev environment; in other words, I could compile
natively.

Because of that, I do not know how various ruby libraries with
extconf.rb and such will react in such a /cross environment.

+--- Kero ------------------------- kero@chello@nl ---+
|  all the meaningless and empty words I spoke        |
|                       Promises -- The Cranberries   |
+--- M38c --- http://members.chello.nl/k.vangelder ---+