From: elise huard <huard.elise@...>
Date: 2010-09-09T04:17:52+09:00
Subject: Re: Nokogiri and LibXML

ah, sorry, I thought the problem was she didn't have the right version
of libxml.  sorry for the confusing advice.

On Wed, Sep 8, 2010 at 2:33 PM, Benoit Daloze <eregontp@gmail.com> wrote:
> 2010/9/8 Une Bévue <unbewusst.sein@google.com.invalid>:
>> Each time i launch a script using Nokogiri i get :
>> WARNING: Nokogiri was built against LibXML version 2.7.7, but has
>> dynamically loaded 2.7.3
>>
>> despit this warning the script works as expected.
>>
>> what is the best way to get right libxml ?
>>
>> my libxml is installed using MacPorts Ruby 1.9 too.
>> Nokogiri is installed rubygems of the ruby 1.9 installed by macports.
>> --
>
> You just need to build Nokogiri against the new libxml2:
> gem install nokogiri
> (and you can remove the old one, if the version was older with gem
> clean nokogiri)
>
> elise: I think this has nothing to do with the packager, in any way
> you still need to build the gem again against the library to match
> version.
> But, yes, homebrew will by default install in /usr/local, which let
> you forget about --with-mylib-dir= option when installing a gem with C
> extension.
>
> (For my part I even had to rebuild Ruby when I moved to homebrew,
> because it was referencing some gmkdir (from coreutils package) in the
> RbConfig, which would cause gems using that to fail to build)
>
>