views:

174

answers:

3

I'm getting started with Parsley (parslets.com), an interesting tool to parse data out of webpages.

http://parselets.com/dev/command%5Fline

I've downloaded the source, built it, and now I'm unable to run it:

parsley: error while loading shared libraries: libparsley.so.0: cannot open shared object file: No such file or directory

I'm a bit of a *nix newbie, so I'm stuck on this.. here is what I did:

  1. I'm using Ubuntu 9.04 64bit
  2. I downloaded the source
  3. I ran "sudo ./configure" and installed dependencies (using apt-get) as necessary
  4. I ran "make install"
  5. I attempted to run parsley by typing "parsley"

Any ideas? thanks.

  • Alex
A: 

It appear that this file must be compiled from the source that you have You should type 'make' first before 'sudo make install' It will compile the parsley.c file to parsley.so.0

sohaibafifi
Thanks for the suggestion, but no luck. I typed 'make' and it essentially said nothing to do. Make install did in fact build it, there is a libparsley.so.0 in .libs, which looks like a symbolic link to libparsley.so.0.0.0 which exists.
Alex Black
Any chance this is a 32bit/64bit issue?
Alex Black
A: 

What does "ldd parsley" say? Chances are ldd doesn't find libparsley.so.0 either.

If so, the problem is that "make install" didn't install libparsley.so.0 into the right place. Find that right place, and move libparsley.so.0 (as well as libparsley.so.0.0.0) there (I believe on 64-bit Ubuntu /usr/lib32 is the right place if libparsley.so.0.0.0 is a 32-bit library, and /usr/lib (or /usr/lib64) if it is a 64-bit library).

Employed Russian
The problem seems to have resolved itself, bizarre. I had another problem resolve itself yesterday too... I did install the suggested updates on Ubuntu yesterday, maybe something broken got fixed?
Alex Black
A: 

The problem seems to have gone away, or at least I can't say I did anything to fix it but it no longer happens. My only guess (grasping at straws) is that when I installed the suggested updates for Ubuntu yesterday something changed or got fixed that affected this.

Update: It turns out, I needed to run:

sudo ldconfig

What must have happened is updating my system ran that for me.

Alex Black