Re: arm64 update - help wanted
+++ peter green [2014-05-16 03:43 +0100]:
> Antonio Terceiro wrote:
> >The code is ported, but starting at 1.9 Ruby needs an existing Ruby
> >interpreter to build. Ruby 1.8 needs only gcc-4.6 ... which needs
> >patchutils. So we got ourselves a loop there.
> I would think that during bootstrapping core packages like gcc and
> patchutils would be crossbuilt. I would suspect that the reason
> gcc-4.6 is not available on arm64 is that noone has bothered to port
> a version of gcc that is now three releases behind current.
Correct. but in fact ruby1.8 builds fine with gcc-4.8. I just did it.
Sadly this handy bootstrap route is going to go away in future and
ruby will become yet another painful self-bootstraping language.
> >I have just committed a change to ruby that AFAICT will actually allow
> >it to be built against ruby1.8 ( http://deb.li/nZlv ),
This will be very handy, as it avaids having to hack about with
symlinks to get the effect of the ruby-defaults packages (which of
course depend on the ruby2.1 I'm trying to build).
> 1: use the packages from ubuntu in your build environment.
> 2: crossbuild ruby (assuming that doing so is possible)
In the long term I think this might be the best thing to get working.
> 3: see if you can get ruby 1.8 to work with a recent gcc.
Done, but ruby1.8 is due to be removed from Debian so won't help in the future.
> I'm ccing this to the removal bug for ruby 1.8 as if it is the only
> way to bootstrap then it might be a good idea to keep it arround.
That would be fine by me, but I'm guessing that at some point it will
become too old to work for this?
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
Reply to: