Skip to main content
Topic: glabels refuses to run (Read 983 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

glabels refuses to run

I have a problem starting glabels-3
I have installed glabels via pacman  (pacman -S glabels)
and tried to run it. Unfortunately it can not start due to a missing shared object:
labels-3: error while loading shared libraries: libxml2.so.2: cannot open shared object file: No such file or directory
When I query the libxml2 package (where I think the missing so should be included?) it seems as it is already installed:
[manoca@ormel ~]$ pacman -Q libxml2
libxml2 2.14.3-1
[manoca@ormel ~]$

So what am I missing?
Any suggestions on this issue?
as always, correct me if I'm wrong ;)

Re: glabels refuses to run

Reply #1
glabels seems to be from Arch's extra repository, and compiled against libxml2 2.14.2, so you'll have to wait until Arch fix it.

 

Re: glabels refuses to run

Reply #2
thanks for that input. Yes, glabels comes from the "extra" repo.. Well I'll wait then. Or does anyone know if there is another software with which I can layout labels for ZPL(glabels seems to be able to do so)?
as always, correct me if I'm wrong ;)

Re: glabels refuses to run

Reply #3
thanks for that input. Yes, glabels comes from the "extra" repo.. Well I'll wait then. Or does anyone know if there is another software with which I can layout labels for ZPL(glabels seems to be able to do so)?
Another option would be to get the build files and build the package locally.
Then it will compile against the libxml2 you have installed. This works most of the time.


Re: glabels refuses to run

Reply #5
Same problem

fuse (UNIX ZXSpectrum emulator) looks for libxml2.so.2
fuse: error while loading shared libraries: libxml2.so.2: cannot open shared object file: No such file or directory

pacman -Ql libxml2 --> I only copy here the lib directory:
libxml2 /usr/lib/
libxml2 /usr/lib/libxml2.so
libxml2 /usr/lib/libxml2.so.16
libxml2 /usr/lib/libxml2.so.16.0.3

No "libxml.so.2" just "libxml2.so". Perhaps a symblink may repair this but I prefer a "clean" update.