You can build libxml on its own (i.e. from source with a --prefix to
an out of the way directory) in another location and link to it. If
you do not use a common location like /usr/local then nothing is
going to find it by mistake. You'll just have to make sure the rake
build finds it.
Dan
Dan,
thanks for the time. My client is not willing to upgrade any of their
libs on the machine I'm deploying to, so unfortunately, this is dead
in the water for me. I will however keep this in mind for future
projects.
Thanks again,
- jason
On 9/13/07, Dan Janowski <[EMAIL PROTECTED]> wrote:
>
Your libxml2 is 3 years old and a minor rev back. Chances are it is
just too old. You have 2.5.10, libxml2 is at 2.6.30 as of august. Try
a build with a current release of libxml2.
Dan
On Sep 13, 2007, at 19:31, Jason Lee wrote:
> xmlreader.h did not have that enum. This is the rpm info:
>
>
xmlreader.h did not have that enum. This is the rpm info:
Name: libxml2-develRelocations: /usr
Version : 2.5.10Vendor: CentOS
Release : 7 Build Date: Fri 12 Nov
2004 11:22:32 AM PST
Install Date: Sat 08 Sep 200
On 9/12/07, Charlie Caroff <[EMAIL PROTECTED]> wrote:
> Well, I do -- it's in /usr/local/bin/iconv
>
> Does libxml expect it in a different location?
Do you have the headers installed? Where is iconv.h? I'm not familiar
with BSD but for Debian, for example, one would have to make sure the
correspo
