First of all, thank you for the update LM! I can't wait to try the fill tool. It looks like it will save a lot of time.
I am trying to use moho 5.4 on a Fedora Core 4 box, and I get the error:
/home/c180391/bin/Moho-5.4/moho.donotrunme: error while loading shared libraries: libpangocairo-1.0.so.0: cannot open shared object file: No such file or directory
I've done some googling for that library, but I'd prefer a "clean" solution and not hack something together.
Thanks!
jorgy
EDIT:
After digging some more, it looks like that library is provided in pygtk2 in Fedora Core 5, but not in Fedora Core 4. Is there any reason why moho now requires this, or was it just compiled on a newer distro?
I had a similar thing with libstdc++ (version 6)..
To fix it I just got a copy of libstdc++.so.6.0.7 from a friend of mine, and renamed it to libstdc++.so.6 and threw it in moho's launch directory..
afaik the minor version number doesn't affect the.. change..
Another solution is to copy the lib to /usr/lib and then make a symbolic link with the same name as what moho requires.. This would work too..
The Pango (internationalized text renderer) is a subsystem of the Gnome desktop environment. Perhaps Moho's gtk widgets are using it. Perhaps you have only KDE on your computer. Try to install Gnome.
/home/c180391/bin/Moho-5.4/moho.donotrunme: /lib/libc.so.6: version `GLIBC_2.4' not found (required by /home/c180391/bin/Moho-5.4/libpangocairo-1.0.so.0)
/home/c180391/bin/Moho-5.4/moho.donotrunme: /lib/libc.so.6: version `GLIBC_2.4' not found (required by /home/c180391/bin/Moho-5.4/libcairo.so.2)
It's wanting a different version of glibc! Talk about going down a rabbit hole! Everything depends on glibc.
I'm not quite ready to go to FC5 on my main box, but I use moho so much it may force me...
Fazek:
I do have gnome installed - thanks for the suggestion.
It is possible to use a more recent version of glibc, but you have to upgrade the kernel etc. (practically everything in the /boot directory) and many libraries. You can keep the old glibc and all of the old libraries for the programs really want it (but most of the programs are running with the new glibc without any problems). I made such change on a computer years ago, it was very hard and required to start the rescue system from a CD many times, but it was successful and it is still working well. I used a SuSE distribution, so maybe your system is different. This change is extremely dangerous to your system's integrity so don't do it, unless you are really sure. There will be continuous problems with the contents of the /usr/include directory when compiling programs.
Perhaps you can copy all of your computer's data to a separate harddisk first, and try to make the upgrade on this harddisk. If something fails, your original system is safe.
Other solution and maybe it is better: Try to find the Pango source and compile it to your system by hand. I think it won't be easy because it is connected to gtk and others (I didn't see two compatible gtk versions yet) so maybe you have to modify the source to fit to your system. You need the development packages of gtk and others (glib, gdk, ...?)
