Ruby/ruby+oniguruma build failure

[Tim Hammerquist]

J. W. Ballantine wrote:
> I'm trying to do a portupgrade on a new 6-RELEASE, and I'm
> getting a patch error on Ruby/ruby+oniguruma.  I blew away the
> devel/onigurmuna port and re-cvsup'ed on Sunday AM and I'm
> still getting the error.
> 
> What am I missing??
> 
> Thanks
> 
> Jim Ballantine
> 
> ** Detected a package name change: ruby (lang/ruby18) -> 'ruby+oniguruma' 
> (lang/ruby18)
> --->  Upgrading 'ruby-1.8.2_4' to 'ruby+oniguruma-1.8.3' (lang/ruby18)
[ snip ]
> patch -d /usr/ports/lang/ruby18/work/ruby-1.8.3 -p0 < ./re.c.181.patch
> Hmm...  Looks like a unified diff to me...
> The text leading up to this was:
> --------------------------
> |--- re.c.ruby_orig	2003-11-04 18:13:57.000000000 +0900
> |+++ re.c	2004-04-26 12:05:31.000000000 +0900
> --------------------------
> Patching file re.c using Plan A...
> Hunk #1 succeeded at 483 (offset 42 lines).
> Hunk #2 succeeded at 581 (offset 40 lines).
> Hunk #3 failed at 591.
> Hunk #4 succeeded at 807 (offset 110 lines).
> Hunk #5 succeeded at 811 (offset 40 lines).
> 1 out of 5 hunks failed--saving rejects to re.c.rej

I got the same issue while portupgrading my 5.4-R to 6.0-stable.

It seems that the C file (re.c) against which the rejected patch
was taken has changed.  Only one line seems to have been added,
but in an inopportune place.

My situation differed in that I actually chose to build ruby
with the oniguruma option.  Removing the relevant option file
from /usr/db/ports/ and rebuilding w/o oniguruma support
provided a successful build.

However, I'm looking forward to using ruby with the new
oniguruma engine!

HTH,
Tim