cvs commit: ports/x11-toolkits/ruby-gtk2/files patch-rbgtkrecentfilterinfo.c

[Steve Wills]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/06/11 16:01, Philip M. Gollucci wrote:
> On 12/06/11 20:21, Steve Wills wrote:
>>> Really ?  UTF8 in comments ?  GCC should handle that though not
>>> technically valid C89/99 I forget.  Its clang/sun compiler that yells.
>>>
>>>
>>
>> GCC has nothing to do with it, unfortunately. The file in question is
>> parsed by ruby and a regex is applied. Ruby 1.9 complains with:
>>
>> extconf.rb:123:in `block (2 levels) in run': invalid byte sequence in
>> US-ASCII (ArgumentError)
>>
>> Apparently it's unwilling to perform a regex on data that it thinks should
>> be US-ASCII only but turns out to be UTF8? I'm not sure. If you find a
>> better solution, by all means let me know.
> 
> Update extconf.rb:123 to use the /u flag in the regex. Though I'm not
> sure why the comment has multi-byte stings to begin with.
> 

Thanks, good idea. Unfortunately, it didn't solve the problem. Putting
Encoding.default_external="UTF-8" at the top of extconf.rb did, but it's
not worth bothering with for now, IMHO. I'll get it next time.

Thanks,
Steve
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (FreeBSD)

iQEcBAEBAgAGBQJO3txjAAoJEPXPYrMgexuhf4YH/0J6eo24NfIS9H4xDNbXh5qZ
O/R0OFesjy5ONlrvjsWei4Wd7H4l3m8m4J1Lo8Q3JuA/PzJH2VwSxyC40YXH4HAP
1jTlPR4mvyjvdR0V4QIPWH2TEFpBKgK5JrjTsxQ28EeVIf0YQ7OapdwOMCofzx7E
5JuUtoaeR/GPp9a+bp5o0vcnnL7ZRMQ0XEUwq9StAX6w/MVr2Vwl+tPsFGXfBo2N
Vn3/ixq2JoIzIO4V1cbwBFkTkMnd8nS92bdNWEqQhy+BYx9UvSHCR7Px1faTfIaG
hr3Q/ld/LwNxjomhN8yJPZSyx7xvB8+Krf4EAPZGjbZqLOSLGTS+JmdVeAqx9T8=
=Ut1o
-----END PGP SIGNATURE-----