Speaking of llvm-gcc, is the problem with clang and llvm-gcc builds not passing the test suite still there, or has that been fixed?
On Nov 25, 2009, at 17:15, source_chan...@macosforge.org wrote:
> Revision
> 3054
> Author
> lsansone...@apple.com
> Date
> 2009-11-25 15:15:05 -0800 (Wed, 25 Nov 2009)
> Log Message
>
> fix llvm-gcc build
> Modified Paths
>
> MacRuby/trunk/string.c
> Diff
>
> Modified: MacRuby/trunk/string.c (3053 => 3054)
>
> --- MacRuby/trunk/string.c 2009-11-25 21:45:31 UTC (rev 3053)
> +++ MacRuby/trunk/string.c 2009-11-25 23:15:05 UTC (rev 3054)
> @@ -5320,7 +5320,7 @@
> return ((rb_bstr_t *)bstr)->data;
> }
>
> -inline void
> +void
> rb_bytestring_set_wrapped_data(VALUE bstr, CFMutableDataRef data)
> {
> GC_WB(&((rb_bstr_t *)bstr)->data, data);
> _______________________________________________
> macruby-changes mailing list
> macruby-chan...@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-changes
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
