[XML-SIG] Re: [4suite] from CNR - Italy

[Jeremy Kloth]

> "Martin v. Loewis" wrote:
> >
> > > What OS are you on?  It looks like pyexpat did not get
> > > compilied/installed properly.
> > [...]
> > > > ImportError: libexpat.so.0: cannot open shared object file: File o
directory inesistente
> >
> > Do you have a libexpat.so.0 on your system? If so, you need to set
> > your LD_LIBRARY_PATH to point to the directory containing it.
> >
> > Of course, it is confusing that pyexpat would link with a shared
> > libexpat that cannot be found. This is most likely an error. To
> > investigate it, we need to know in detail what you did to install
> > PyXML. I.e. please report
> >
> > - what system you are using
> > - what file you've downloaded to install PyXML (exact URL please)
> > - what commands you've used in what order to install PyXML
> >
> > If you could give further clues (e.g. why it might think to use
> > libexpat.so.0), don't hesitate to communicate them as well.
>
> The funny thing is that on my Red Hat 7.1 system, it isn't
> "libpyexpat.so.0" that is built by PyXML, but rather
>
> /usr/local/lib/python2.1/site-packages/_xmlplus/parsers/pyexpat.so
>
> Looking at the code, I don't see why on earth it would be looking for
> "libpyexpat.so.0" on UNIX.
>

Now, PyXML only builds pyexpat if the version of pyexpat included with
Python is less than 2.39.  And if I remember correctly, pyexpat from Python
links against the expat libary, hence the failed libexpat.so.0.

I don't have a copy of Python 2.0.1 around to check the version of pyexpat,
however, in 2.1 it is 2.45.  If they rolled changes in pyexpat into the
bugfix release, this would account for this odd error.

--
Jeremy Kloth                              Consultant
jeremy.kloth@fourthought.com              +1 303 583 9900 x 105
Fourthought, Inc.                         http://fourthought.com
4735 East Walnut St, Boulder, CO  80301, USA
XML strategy, XML tools (http://4suite.org), knowledge management