shouldn't this be centralized, i.e. in ruby.port.mk when setting the
default version?
On Mon, Jan 6, 2014 at 6:06 PM, Jeremy Evans <jeremyeva...@gmail.com> wrote:
> On Mon, Jan 6, 2014 at 9:42 AM, Markus Lude <markus.l...@gmx.de> wrote:
>
> > Hello,
> >
> > with the update of swig to 2.0.11 it doesn't build any more on sparc64.
> > MODULES lang/ruby uses ruby 2.0 per default now, which doesn't build on
> > sparc64. Does the new swig need the new ruby or is ruby 1.8 enough?
> >
>
> It still packages on amd64 with "MODRUBY_REV = 1.8". I suppose something
> like this may work if we want to build swig on sparc64/hppa/alpha without
> holding other arches back:
>
> .if ${MACHINE_ARCH:Msparc64} || ${MACHINE_ARCH:Mhppa} ||
> ${MACHINE_ARCH:Malpha}
> MODRUBY_REV = 1.8
> .endif
>
> Thanks,
> Jeremy
>
