On Jan 29, 1:59 pm, Sam Ruby <[EMAIL PROTECTED]> wrote:
> Two things:
>
> I'm trying to port a number of projects to Ruby 1.9. Current status can
> be seen here:
>
> http://intertwingly.net/projects/ruby19/logs/
>
> I'd like to try libxml2, presuming that people would be interested in
> acceptin
Hey guys,
Im trying to install the libxsl gem on OSX, but keep getting this error:
ldruby_xslt_transform_context.o:
symbolld(:s )symbol (nots )found notfor foundarchitecture forppc
architecture i386
collect2: collect2: ld returned 1 exit statusld returned 1 exit status
lipo: can't open in
Trans wrote:
>
> I updated the Rakefile to shell out to the task/* scripts.
Thanks!
With the attached patch, I've the following sequence works on Ruby 1.9,
revision 15360 (the latest HEAD):
rake clobber
rake compile
rake test
The patch should not be applies as is, as the rename of ut
Sam Ruby wrote:
Trans wrote:
I updated the Rakefile to shell out to the task/* scripts.
Thanks!
With the attached patch, I've the following sequence works on Ruby 1.9,
revision 15360 (the latest HEAD):
rake clobber
rake compile
rake test
The patch should not be applies as is, as
has anyone done any work getting libxml to work on/with Rubinius?
--
thanks,
-pate
-
Duty makes us do things, Love make us do things well.
http://on-ruby.blogspot.com http://on-erlang.blogspot.com
http://on-soccer.blogspot.com
___
Dan Janowski wrote:
> Hi Sam,
>
> Thank you for tracking these changes. In the interest of tracking all
> changes so they may be properly applied, please submit this to the
> patch tracker at this location:
>
> http://rubyforge.org/tracker/?func=add&group_id=494&atid=1973
>
> Dan
Done:
htt
Hi Sam,
Thank you for tracking these changes. In the interest of tracking all
changes so they may be properly applied, please submit this to the
patch tracker at this location:
http://rubyforge.org/tracker/?func=add&group_id=494&atid=1973
Dan
On Jan 31, 2008, at 10:15, Sam Ruby wrote:
> S
My thanks to all of you for using, discussing, reporting and
contributing to the ruby-libxml extension. As more people become
involved and as the quantity of contributions and issues grows, it has
become more difficult to keep track of what needs to be done. With
this in mind, the following
This entices me. The MRI internals (esp. the GC) are the biggest
obstacle to making this library work and I am beginning to really hate
them. I've even had this delusion that making this library work with
Subtend may enable effective repair of outstanding faults more easily
than trying to d
